Zughafen Kulturbahnhof GmbH's tech stack
What does Zughafen Kulturbahnhof GmbH use?
Zughafen Kulturbahnhof GmbH (zughafen.de) uses at least 12 tools we can see from public records, including Google Analytics for analytics, WordPress for its website, CleverReach for marketing and Cloudflare for content delivery. Last checked .
- Industry
- Events Services
- Size
- 1–10 employees
- Based in
- Erfurt, Germany
- Founded
- 2002
- Company page
- Tools found
- 12
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Zughafen Kulturbahnhof GmbH'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.
Edge & Hosting
1 tool, where the bytes are served from
CDN & Edge
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
6 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Zughafen Kulturbahnhof GmbH tech stack FAQ
What tools does Zughafen Kulturbahnhof GmbH use?
We've found 12 tools at Zughafen Kulturbahnhof GmbH (zughafen.de). Edge & Hosting: Cloudflare. Application: jQuery, Vimeo and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, WordPress and Yoast SEO. Last checked October 3, 2026.
What analytics tools does Zughafen Kulturbahnhof GmbH use?
Zughafen Kulturbahnhof GmbH uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Zughafen Kulturbahnhof GmbH use?
Zughafen Kulturbahnhof GmbH uses WordPress, Yoast SEO and WooCommerce for its website. We found WordPress through website code.
What marketing software does Zughafen Kulturbahnhof GmbH use?
Zughafen Kulturbahnhof GmbH uses CleverReach for marketing. We found CleverReach through email records.
Does Zughafen Kulturbahnhof GmbH use Cloudflare?
Yes. We found Cloudflare at Zughafen Kulturbahnhof GmbH through DNS records. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Zughafen Kulturbahnhof GmbH uses?
We read public traces only: Zughafen Kulturbahnhof GmbH'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.