runsonwhat

Technische Werke Ludwigshafen's tech stack

What does Technische Werke Ludwigshafen use?

Technische Werke Ludwigshafen (twl.de) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and Usercentrics for security. Last checked .

Industry
Public Utility
Based in
Germany
Founded
1973
Tools found
9
Categories
7
Layers
4 of 5
Last checked
Oct 2026

Technische Werke Ludwigshafen'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

2 tools, what the product is built with

Media & UI

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

Technische Werke Ludwigshafen tech stack FAQ

What tools does Technische Werke Ludwigshafen use?

We've found 9 tools at Technische Werke Ludwigshafen (twl.de). Application: jQuery and YouTube. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Microsoft 365, Apple Business and Usercentrics. Last checked October 2, 2026.

What email provider does Technische Werke Ludwigshafen use?

Technische Werke Ludwigshafen uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does Technische Werke Ludwigshafen use?

Technische Werke Ludwigshafen uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does Technische Werke Ludwigshafen use Microsoft 365?

Yes. We found Microsoft 365 at Technische Werke Ludwigshafen through DNS verification records. Microsoft 365 is used by 261,694 companies we track.

How does runsonwhat know what Technische Werke Ludwigshafen uses?

We read public traces only: Technische Werke Ludwigshafen'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.