Flight Tracker vs. Train Tracker: Why Trains Are Harder to Track

Updated: August 2026 – The difference between flight tracking and train tracking is the most common disappointment in live tracking: with aircraft, you can see every plane worldwide accurate to the second; with trains, symbols jump, freight trains are missing, and whole routes disappear. That’s not down to bad apps, but to two fundamentally different data architectures. This comparison explains why – and what you can still get out of train maps.

Why does flight tracking work better than train tracking?

Flight tracking works better because aircraft broadcast their position themselves, openly. Via ADS-B, an aircraft determines its position by satellite navigation and transmits it unencrypted as a radio message – anyone with a suitable receiver can pick up this data. Trains don’t do that: they report their position to the operator via closed operating systems, and what becomes public from that is decided by the transport company.

Practically everything else follows from this one difference. Flight data is an open raw data stream, rail data is a filtered product of passenger information. That’s why flight positions are accurate to the second and train positions are calculated; that’s why cargo flights are visible and freight trains aren’t. The rail data chain is described in detail in the overview on live tracking for trains and buses.

How aircraft positioning works technically

ADS-B stands for Automatic Dependent Surveillance – Broadcast. The name describes the method precisely:

• Automatic: the aircraft transmits on its own, without being queried from outside.
• Dependent: the position comes from the onboard satellite navigation, not a ground measurement.
• Surveillance: identifier, position, altitude, heading and speed are transmitted.
• Broadcast: the message goes out unencrypted to anyone listening.

There’s a second, often underrated factor: propagation physics. An aircraft at cruising altitude has a clear line of sight over very large distances. A single receiving station can therefore cover an area that would need dozens of stations at ground level. That’s exactly why worldwide receiver networks made up mostly of private stations could emerge – with comparatively little effort per area covered.

The third factor is regulatory: in large parts of controlled airspace, ADS-B equipment is mandatory for the aircraft categories concerned. An open standard, plus an equipment mandate, plus cheap receivers – this combination simply doesn’t exist in rail.

How train positioning works instead

Trains also know very precisely where they are. It’s just that this knowledge stays within the system.

Positioning for operations, not for the public

Rail operators locate vehicles through a mix of trackside technology and vehicle reports: track-vacancy detection systems from DB InfraGO detect which section is occupied, train protection systems report passages at defined points, and operational radio transmits status information. The result feeds into control systems built for running operations – not for map displays.

Only passenger information gets published

From this internal data, what travellers need is derived: departure time, delay, platform, forecast. It’s exactly this reduced stream that apps and maps read. The consequence: anything that isn’t passenger information – freight trains, empty stock movements, light engine moves, engineering trains – practically doesn’t exist in this data. How to track such workings anyway is shown in the guide to tracking freight trains.

Maps interpolate between reports

Between two reporting points, map applications estimate the position based on the timetable and the route. That’s why symbols move smoothly even though the data source doesn’t actually support that – and why they jump as soon as a real report corrects the estimate. You’ll know the same effect from the world of buses, where it’s described in the guide to real-time bus tracking.

Dimension	Air traffic (ADS-B)	Rail traffic (public data)
Data origin	Vehicle broadcasts itself, openly	Operator reports internally, published filtered
Position accuracy	Measured GNSS coordinate	Estimate calculated onto the route
Update rate	Seconds	Typically several tens of seconds to minutes
Coverage	Near-complete wherever receivers stand	Depends on data release by each operator
Freight/cargo	Cargo flights visible like passenger flights	Freight trains largely invisible
Vehicle link	Identifier identifies the specific aircraft	Trip number, no direct vehicle link
Receiver network	Can be privately run, long range	Practically not replicable at ground level

Is a genuine train radar even possible?

Looked at soberly, a train radar in the Flightradar sense isn’t a software problem someone could solve, but a matter of standards, physics and interests. If you wait for it, you’ll be waiting a long time. If you work with the sources that already exist instead, you can get a long way today – as the comparison live train radar: the best tools and maps shows.

What this means for your live tracking in practice

Five very concrete rules of thumb follow from this system logic.

Where rail data actually beats air traffic

The comparison doesn’t fall entirely in aviation’s favour. Rail clearly wins on three points.

• Forecasts. Because a timetable with fixed stops is stored, a rail system can say when a train will be where – not just where it currently is. Air traffic doesn’t have this kind of prediction.
• Connection information. Control systems know interchange relationships and can protect connections. A pure position broadcast can’t do that in principle.
• Reference to the timetable. A delay in minutes is a solid statement about deviation from the plan. For flights, the comparable information is much coarser. The guide to regional transport associations and live departures per station shows how to make use of this strength.

Put another way: flight tracking answers “where is it now” better, rail systems answer “when will it be there” better. Anyone tracking long-distance services makes use of exactly this strength – the guide to real-time ICE tracking turns it into a method.

What the comparison with ships and buses shows

The contrast becomes even clearer if you put two more modes of transport alongside these two. Both sit exactly between aircraft and trains – and for the same structural reasons.

Ships broadcast via AIS in a similarly open way to aircraft: position, heading and identifier are transmitted by radio and can be received by anyone within range. Range is lower than in the air, but there are hardly any obstacles over water – which is why ship maps work remarkably well near the coast and only work far out to sea with additional satellite receivers. The same rule applies here too: an open standard plus free propagation makes for a good map.

Buses sit closest to trains. They locate themselves via GNSS but report to a control system rather than broadcasting. What becomes public is again filtered passenger information with reporting intervals of several tens of seconds. That’s exactly why bus symbols jump around on maps for the same reasons as train symbols – the cause is identical, only the operator differs.

From this you can derive a general rule that applies to any mode of transport:

• Does the vehicle broadcast itself, openly? Then good live maps exist.
• Does it report to a closed system? Then everything depends on the operator’s data release.
• How far does the signal reach? A few kilometres at ground level, many times that in the air and over water.
• Is there a commercial reason for holding back? Almost always with freight, rarely with passenger transport.

For spotters, the practical consequence is the same everywhere: the more closed the system, the more important your own observation becomes. For aircraft, the map is the main source; for trains, it’s an aid alongside timetable knowledge and the community.

Common mistakes in the comparison

• Blaming the app. Missing trains are almost never down to the application, but to the data release of the company in question.
• Mistaking interpolation for measurement. Smooth movement on the map suggests a data density that doesn’t exist.
• Looking for freight trains in real-time data. They’re structurally not included there – no filter in the world will bring them up.
• Relying on a single tool. Every source has different gaps; two sources cover for each other. The overview of DB train radar alternatives sorts through which types exist.
• Ignoring diversions. On routes not stored in the system, the projection is systematically wrong, not just imprecise.
• Waiting for a future “real” train radar. The obstacles are structural in nature. It’s more practical to work with what’s there – as described in the practical guide how to track a moving train.

Conclusion

The comparison between flight tracking and train tracking ultimately comes down to a comparison between an open broadcast and a closed operational report. As long as trains don’t broadcast their position themselves and publicly, there won’t be a rail map that feels like flight tracking – no matter how well an app is programmed. That’s not bad news, though, but useful: once you know the cause, you stop looking for the perfect app and instead build yourself a working combination of timetable data, train numbers and your own observations.