Zugradar 24 and Bahnradar: What's Behind the Names?

Updated: August 2026 – Zugradar 24, Bahnradar 24, Zugmonitor, Zug Radar live: if you look for a live map of trains in Germany, you end up in a muddle of names in which it’s hard to tell what is a product, what is a project and what is merely a search phrase. This article sorts out the terms, explains where the data behind such maps really comes from, and gives you five test criteria you can use to assess any radar site yourself.

What’s really behind “Zugradar 24”

“Zugradar 24” (German for “train radar 24”) is not a product name but a search phrase. Users borrowed the suffix “24” from flight tracking, where a well-known service carries it in its name; transferred to the railway, it simply expresses the expectation that something similar ought to exist for trains. Accordingly, such searches lead to very different destinations: official timetable information services, transport association maps, community projects, aggregators and plain advertising sites that target the search term without having any data of their own.

The second misconception lies in the word “radar”. Trains are not detected by radar. Their position is derived from reports from the vehicle or from operating locations and then calculated against the scheduled timetable. What appears on a map as a smoothly moving dot is therefore a calculated position along the route – a principle that the overview of live tracking for trains and buses explains in detail.

The names sorted: what belongs where?

It helps to sort the terms by their origin rather than by how they sound.

• Zugradar / Zug Radar live: generic terms for live maps of train traffic. No single provider clearly owns the term.
• Bahnradar 24: the same construction with “Bahn” (railway) instead of “Zug” (train). The search queries differ, the expectation behind them is identical.
• Zugmonitor: the name originally comes from data journalism, where delay data was mapped and made publicly accessible. Projects like this are often time-limited.
• Transport association and operator maps: services from transport companies and transport associations. They rarely have “radar” in their name but provide the most reliable data for their area.
• Spotter and community platforms: they don’t show positions but sightings and vehicle allocations – a different type of data.

Where the data comes from – and why that decides everything

At its core, a live map is just a presentation. Its value depends on the source underneath. Three origins need to be distinguished.

Operational data from the transport operators

Vehicles and operating locations report positions and events to the operators’ control systems. The reporting points themselves belong to the infrastructure – in Germany mostly to the network of DB InfraGO, the infrastructure manager – and not to the respective railway operator. From this come minutes of delay, forecasts and connection information. This data is the most reliable basis, but it is not published everywhere or in full.

Timetable data

The scheduled timetable is the second ingredient. Without it there would be no delay, because there would be nothing to deviate from. When there is no real-time report, many maps simply keep showing the timetable position – the display then runs smoothly without having anything to do with reality any more.

Observations from the community

Sightings are not position data but evidence. They answer questions that in principle cannot be derived from operational data: which coach is working the service, which locomotive is at the head of the freight train, which vehicle is running on the replacement service. How to use this source systematically is shown in the guide to live sightings in real time.

The comparison: which source for which question?

Instead of pitting provider names against each other, it’s more productive to ask which type of source solves your problem.

Type of source	Mainly answers	Typical strength	Typical gap	Relevant for spotters if …
Operator’s official timetable information	When is my connection coming?	forecasts, connections, disruption notices	no vehicle allocation	you’re following a specific journey
Transport association and regional services	What’s running in my region?	dense coverage in their own area	ends at the association boundary	you’re planning locally
General live train maps	What’s on the move where right now?	overview of larger areas	freight and special runs are usually missing	you want to get an overview
Community sightings	Which vehicle is running?	vehicle reference, special services, replacement services	no comprehensive live position	you’re looking for a particular vehicle
Forums and sightings threads	What unusual traffic is out there?	context, experience, diagram tips	unstructured, delayed	you want to track down special runs
Operator disruption services	What’s broken right now?	diversions and closures	no tracking of individual trains	you want to photograph diverted trains

If you want to compare the specific tools behind these types, you’ll find the detailed comparison in the Zugradar live comparison of the best tools. For simply following a single journey, the guide on how to follow a moving train is also worth a look.

Five test criteria for any radar site

The most important of these points is the first. A map that doesn’t say where its data comes from can show anything – including just the timetable. And a timetable looks just as convincing on a map as real real-time data, but is useless precisely when you need it most: during disruptions.

What radar maps fundamentally can’t do

For spotters, the first point against is the decisive one. Whether an ICE is on time helps when travelling; whether it’s the ICE you’re waiting for decides the picture. For long-distance services, the guide to tracking the ICE live helps, and for allocation via numbers, the guide to tracking DB train numbers. And if you’re specifically after freight, the guide tracking freight trains live shows the detours that become necessary because the radar maps are silent here.

How to tell that a map only shows the timetable

The most common mislabelling on live maps isn’t a forgery but an omission: the site shows timetable positions and calls them “live”. As long as everything runs on time, the difference goes unnoticed. But there are three reliable cross-checks.

The disruption test. Look at the map when you know a line is disrupted – for example after a reported line closure. A timetable-based map lets the trains keep running obediently. A map with real operational data shows standstill, gaps or no journeys at all.

The delay test. Look for a journey that you know from official timetable information is significantly delayed. If the map shows it at its scheduled position, it isn’t working with real-time data.

The night test. In the hours without passenger traffic, a map should be largely empty. If it constantly shows evenly distributed dots, that’s a clear sign of simulated movement.

Together, these three tests take five minutes and save you from planning mistakes. Importantly: a timetable map isn’t worthless – it’s just something other than what it promises. For the rough question of when anything runs on a line at all, it may well be enough.

Common mistakes when looking for the right Zugradar

• Searching by name instead of by function. “Zugradar 24” is a search term, not a service. Instead, put into words what you want to know.
• Confusing looks with data quality. A pretty map can run on pure timetable data. The question is always what happens when reality deviates from the plan.
• Overlooking regional boundaries. Many services are limited to one transport association. For journeys beyond its boundary, you need regional transport association departure information on both sides.
• Reading a missing display as a cancellation. If a train disappears from the map, it usually keeps running – just without reports.
• Relying on a single source. If you’re planning a long journey, compare at least two independent sources.
• Taking test reports as facts. Features and terms change. What counts is on the provider’s site, not in an article from the day before yesterday.

What you can do instead

Instead of continuing to look for the one perfect radar, a threefold approach pays off: an official source for delays, a regional source for coverage and a community source for the vehicle question. In practice, this combination is more stable than any single tool, because the gaps in one source are filled by the next.

For platforms beyond live maps – where sightings, photos and experience come together – take a look at the comparison of Trainspo alternatives and the overview of Drehscheibe Online alternatives. Neither is a radar service, but for spotters they answer the questions that radar maps fail at.

Conclusion

The name is misleading: “Zugradar 24” promises a product but actually describes an expectation. Once you understand that every live train map is only as good as the operational and timetable data underneath it, you stop looking for the one right site and start choosing sources according to your questions. Five test criteria are enough to assess an unfamiliar map – and if the answer is “no data source given”, the decision is quickly made.