Tracking the U-Bahn Live: Why Tracking Works Differently in Tunnels

Updated: August 2026 – With buses and trams, you see a vehicle glide smoothly across the map. But if you want to track an U-Bahn train live, things quickly get jerky – or you find no map at all, just a departure board. That’s not down to your app, but to the fact that a completely different location technology is at work underground.

Tracking the U-Bahn live: how the position is determined without GPS

An U-Bahn train is not located by satellite but via the train protection system: the line is divided into sections, and the equipment in the track continuously reports to the signal box which section is currently occupied. From this occupancy report, from balises in the track and – on modern lines – from a permanent radio link to the train, the operations control centre builds its picture of the situation.

What reaches your phone is usually just the derivative: a departure forecast for each station. The control centre knows the position of the trains very precisely, but rarely publishes it as a freely usable vehicle position. How differently operators and transport associations handle this release is shown in the real-time comparison of transport associations.

Why GPS fails underground

Satellite signals are extremely weak by the time they reach the earth. Under open sky, a GPS receiver evaluates them from several directions at once. As soon as concrete, soil or a station roof gets in the way, reception drops out. You probably know three effects from everyday life:

• The hard cut-off: as the train enters the tunnel, your phone loses its fix within seconds. The map freezes or keeps extrapolating at the last known speed.
• The false fix: in station halls and cuttings, signals arrive only as reflections. The result is a position that is dozens of metres off.
• The long recovery: after leaving the tunnel, the receiver needs a few seconds until it has enough satellites again. It’s precisely in this window that the display jumps.

For a transport operator, that’s unacceptable. Train protection has to work even when nothing can be received – which is why the position in the tunnel is determined by trackside equipment and not by the vehicle alone. The same logic applies to all tunnel sections, by the way, including those of Stadtbahn (light rail) systems; above ground, on the other hand, the principle that real-time bus location uses takes over again.

The three building blocks of U-Bahn train location

Track vacancy detection: the occupied section

The classic building block is track vacancy detection. It answers just one question: is this section clear or occupied? Two methods are widespread:

• Track circuit: a weak current flows through the rails. If a vehicle is in the section, its wheelsets short-circuit the circuit – the section reports occupied.
• Axle counter: sensors at the start and end of a section count the axles entering and leaving. If both counts match, the section is clear.

Neither provides a position to the metre, only a statement about a part of the line. That is exactly where the typical jumpiness of metro maps comes from.

Balises and odometry: the fine resolution

Between the reporting points, the train does its own calculations. Wheel revolutions and acceleration sensors provide continuous odometry, which is corrected back to zero at fixed points in the track – balises or transponders. Without this correction, wheel slip would add up.

Radio-based train control: the continuous report

Modern, partly automated lines work with a permanent radio link between the train and the line control centre. The train reports its calculated position, and the control centre then grants movement authority up to a calculated point. This allows shorter headways – and, as a side effect, a much finer picture of positions than section occupancy alone could provide. The Copenhagen Metro has run completely driverless on this basis since it opened. The newer line M2 of the Warsaw Metro (Metro Warszawa) is also equipped with such a radio system.

From the occupancy report to the display in your app

Several stages lie between the axle counter in the tunnel and the minutes shown on your display. This chain explains why data sometimes arrives late or not at all.

What you really see in which view

In practice, the crucial question is not “is there real-time data?” but “what kind of real-time data?”. The table sorts the common views.

View	Data basis	Typical resolution	What it’s good for
Station departure board	Forecast from comparing scheduled and actual times	per station, to the minute	The most reliable source for “when is the next train coming?”
Live map with a moving dot	Station reports plus interpolation	estimated between two stations	Rough orientation as to where a diagram is
Line view with train symbols	Occupancy or reporting points	section by section, jumping	Good for seeing how tight the headway currently is
Service disruption notice	Manual entry by the control centre	event-based	The only way to learn about cancellations and diversions
Community sighting	Observation on site	accurate to the vehicle and car	The only source for class, car number and special vehicles

If you want to get the differences between official information and observation clear in general, you’ll find them in the overview of live sightings in public transport and in the comparison of train and bus tracking.

Why metro maps judder – and when it doesn’t matter

A jumping train on the map is not a bug. It is the honest representation of a section-by-section report. It only becomes a problem when an app smooths over the gaps so thoroughly that you assume an accuracy that doesn’t exist.

For spotters, the conclusion is a pleasant one: underground, you need less live data than above ground. If you want to catch a tram in mixed traffic, you’re battling traffic lights and congestion – see the guide on how to follow a moving tram. In the tunnel, you work with the service frequency and knowledge of the diagrams instead.

What this means for spotting at U-Bahn stations

Instead of staring at a dot, you plan with three variables: service frequency, diagram duration and vehicle distribution.

• Read the frequency: if the timetable shows a train every five minutes, you can expect about twelve trips in each direction per hour. That’s a much more solid planning figure than any minute-by-minute forecast.
• Estimate the diagram duration: how long does a train take for the outward and return journey including turning round? That tells you after what interval you’ll meet the same train again – handy if you need a particular set once more.
• Watch the mix of classes: in most networks, several vehicle generations run side by side. Which one is used when is not revealed by any timetable information – only by observation.
• Use off-peak times: early in the morning and late in the evening, platforms are empty, headways are longer and the chance of calm pictures is much higher.
• Check for engineering works: closures and replacement services change diagrams completely. The disruption notice is more important here than any map.

When it comes to composing the picture itself, rules of their own apply – artificial light, mixed light and lots of movement. The guide to U-Bahn photography covers the technique, and for the dark off-peak hours the camera settings for spotting at night will help.

Common mistakes in U-Bahn tracking

• Taking the live map for a measurement. Between two stations, the moving dot is as a rule calculated, not reported.
• Assuming one city applies to all. Every network has its own technology and its own data release policy. In Hamburg the Hamburger Hochbahn decides, in Berlin the BVG – and the two handle it differently. What is visible in one network is completely missing in the next. Which information applies to your region is explained in the overview of regional transport associations and their live departures.
• Planning to the minute. At high frequencies, the gap between two trains fluctuates by more than the forecast resolves anyway.
• Confusing the journey with the vehicle. A diagram is not a car number. If you’re looking for a particular set, there’s no way around keeping your own records.
• Ignoring disruptions. After a signal failure, the order of diagrams often no longer matches the plan for hours.
• Using only one app. The operator’s app, the transport association’s information and community data each have different gaps. Which tools are suited to what is sorted out in the comparison of public transport spotter apps, and for planning locations, your own spotter map helps.

Conclusion

Tracking the U-Bahn live means working with a different data logic than above ground. Instead of a satellite-based vehicle position, you get a forecast derived from the train protection system – very reliable, but coarsely resolved and rarely published as a map. If you accept that, you can actually plan more calmly underground: the service frequency is more stable, disruptions are rarer, and the only really missing piece of information – which vehicle is coming – can only be filled in by looking and recording.