Universitätsklinikum Brandenburg An Der Havel's tech stack
What does Universitätsklinikum Brandenburg An Der Havel use?
Universitätsklinikum Brandenburg An Der Havel (uk-brandenburg.de) uses at least 7 tools we can see from public records, including Google Analytics for analytics and Sophos for security. Last checked .
- Industry
- Healthcare
- Size
- 1,001–5,000 employees
- Based in
- Brandenburg, Germany
- Founded
- 1901
- Company page
- Tools found
- 7
- Categories
- 4
- Layers
- 4 of 5
- Last checked
- Oct 2026
Universitätsklinikum Brandenburg An Der Havel's stack, layer by layer
Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.
Application
1 tool, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Security & Compliance
Universitätsklinikum Brandenburg An Der Havel tech stack FAQ
What tools does Universitätsklinikum Brandenburg An Der Havel use?
We've found 7 tools at Universitätsklinikum Brandenburg An Der Havel (uk-brandenburg.de). Application: jQuery. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel and Google Ads. Company Ops: Sophos and SwissSign. Last checked October 3, 2026.
What analytics tools does Universitätsklinikum Brandenburg An Der Havel use?
Universitätsklinikum Brandenburg An Der Havel uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Universitätsklinikum Brandenburg An Der Havel use Google Analytics?
Yes. We found Google Analytics at Universitätsklinikum Brandenburg An Der Havel through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Universitätsklinikum Brandenburg An Der Havel uses?
We read public traces only: Universitätsklinikum Brandenburg An Der Havel's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.
We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.