Key takeaways
- Yes, but not like a video feed: trains can be tracked live – but the display is an extrapolation between reporting points, not a continuous stream of positions.
- The hard number is the actual time: the real departure time at the last stop is far more reliable than the dot on the map.
- Delay forecasts are calculated results: they change with every reporting point and are not direct measurements.
- Vehicles aren't part of the data: public real-time data describes journeys. Which set is actually running is only known to whoever is watching.
- Gaps are built into the system: freight traffic, special workings and replacement services often don't appear at all, or only incompletely, in standard information systems.
Contents
- 1.Can you track trains live? The short answer
- 2.What “live” actually means for train data
- 3.The data chain: from the report to the map
- 4.How big the gap to reality really is
- 5.Tracking trains in real time: strengths and limits
- 6.How to do a reality check yourself
- 7.When the map shows something that simply isn’t true
- 8.Why forecasts work differently from positions
- 9.Common mistakes with live train tracking
- 10.Conclusion
Updated: August 2026 – The question can you track trains live is usually answered with a curt “yes, there are apps for that.” That’s true, and it’s still misleading, because it raises an expectation the data can’t deliver. This article shows what real-time train data actually is, how big the gap to reality really is, and where the map claims something that isn’t currently true.
What the map doesn't know, the community does
Real-time data shows you the journey – sightings show you which vehicle was actually out there.
Can you track trains live? The short answer
Yes – but here “live” means a continuously updated extrapolation, not continuous observation. A train reports in at defined points along its route; between two such reports, the system calculates from the stored timetable roughly where it ought to be, and plots that point on the map.
That gives you the most important practical rule: the actual time at the last stop the train passed is solid information, while the interim position out on the open line is an estimate. Anyone who keeps these two apart reads every train information display correctly. How that plays out in practice is shown in the guide on how to track a moving train.
What “live” actually means for train data
For an aircraft over the ocean, the reported position is essentially the actual position. For a train in a dense network, things look different, because here the system cares less about the metre and more about the minute: whether a train is standing 300 metres further ahead changes nothing about connections, platform occupation or passenger information. Whether it’s three minutes late changes everything.
That’s why railway real-time data is built around the timetable. It primarily answers the question “how far off schedule”, and only secondarily “exactly where”. The dot on the map is a by-product of that calculation, not an independent measurement.
The satellite-based basis of the positioning is technically barely different from what happens in road traffic – described in detail in the article on how GPS and onboard computer tracking works. On rail, though, three quirks make the difference: the train number as the reference value, the diagram as the planning layer, and the fixed infrastructure of DB InfraGO with defined reporting points.
The data chain: from the report to the map
Several stages lie between the moving train and your display. Each of them can delay, smooth or distort the picture.
- Report from operations. The train passes a defined point and is logged there. The distance between such points is closer together on main lines than on branch lines.
- Matching to the train number. The report is matched to the journey – which is why the train number is the key to everything, as the guide on tracking DB train numbers shows in detail.
- Scheduled-vs-actual comparison. The operations control system compares the actual time with the timetable and generates the delay in minutes.
- Forecast calculation. From the current deviation and the remaining running times, a prediction is generated for all the following stops.
- Publication. The processed data goes out to information systems, displays and third-party providers – each with its own update interval.
- Display in the app. Only here does a set of numbers become a dot on a line. The app additionally interpolates and smooths the data.
How big the gap to reality really is
Rather than a blanket distance figure, it helps to sort things by question. This table shows which questions real-time data answers well, and which it doesn’t.
| Your question | How well real-time data answers it | Why |
|---|---|---|
| Is my train on time? | Well, as long as the last report is fresh | Direct scheduled-vs-actual comparison at the stop |
| How much delay will there be at the destination? | Moderate, with growing uncertainty | A forecast over many intermediate steps |
| Exactly where is the train right now? | Weak between two reporting points | The position is interpolated |
| Which platform will it leave from? | Good, but sometimes only at short notice | Platform changes are dispatched late |
| Which class is running today? | Not at all | Vehicle data isn’t part of the information |
| Is a freight train about to come through here? | Usually not at all | Passenger information systems cover passenger traffic |
For the last two rows you need other approaches. How to observe freight traffic at all is described in the guide on tracking freight trains live.
Tracking trains in real time: strengths and limits
In favour of real-time information
- It answers the punctuality question directly, with no detours
- It's available across the board for passenger services and free to use
- It gives you connection information you couldn't determine yourself
- It warns you early if a delay is building up over the rest of the journey
- It also works when nobody is on site
Where it hits its limits
- The map position between reporting points is an estimate
- Forecasts jump as soon as new reports come in
- Vehicle, class and set don't appear in it at all
- Freight traffic, special and transfer workings are largely missing
- The usual logic breaks down with replacement services and diversions
Observers close the gap
Exactly where official data falls silent – vehicle, special working, diversion – community sightings help.
How to do a reality check yourself
Instead of trusting someone else’s accuracy claims, you can do the comparison yourself in half an hour. Important: only from publicly accessible locations – platforms, bridges, footpaths. Track areas and operational railway land are off limits for any kind of observation.
Pick a location with a clear view
A publicly accessible point with a good view of the line – a bridge or the end of a platform, say. Note exactly where you're standing.
Pick a specific train number
Take a service that will pass you in the next few minutes and open its route in the real-time information system.
Note the display and the time
A screenshot of the map display plus the time to the second. It's important that both belong to the same moment.
Note when it actually passes
When the train actually comes past, note the exact time. The gap to the app's display is your real-world offset at this location.
Repeat several times
A single comparison tells you little. Only after five to ten journeys do you see whether the offset is constant or varies with traffic conditions.
Document the result
Note down how well the display matches at which spot. That note is worth more at your next photo trip than any general accuracy claim.
Safety comes before any measurement
Observe only from publicly accessible areas. You may not enter tracks, trackbeds, signalling equipment or cordoned-off areas – no matter how quiet the line looks. A spot that promises a better view is never worth it.
When the map shows something that simply isn’t true
There are four recurring situations where the display demonstrably deviates from reality:
- Right after an unscheduled stop. The system keeps calculating with the scheduled running time even though the train is standing still. The dot moves; the train doesn’t.
- During diversions. If a train runs over a route that isn’t stored that way, the projection onto the line doesn’t work cleanly. How to spot such situations early is shown in the guide on tracking disruptions and diversions.
- At the end of a train’s run. After the last stop, the service disappears from the information system even though the set is still shunting or heading into the sidings.
- With replacement services. When numbers are swapped or journeys are split, some systems still show the old structure while operations have long since moved on.
Why forecasts work differently from positions
One point is almost always overlooked in discussions: position and forecast are two completely different quantities with different sources of error. The position is a geometric interpolation – it gets worse the further apart two reporting points are. The forecast, by contrast, is a model of the future and gets worse the more uncertainty lies over the rest of the journey.
That gives you two practical rules. First: a forecast for the next stop is usually pretty good, while a forecast for the destination several hours away is more of a general trend. Second: when a forecast jumps noticeably, that isn’t an error, it’s a correction – the system has received information it didn’t have before.
In practice that means: plan around the forecast for the next stop, not the one for the destination. And if you’re waiting at a spot, go by the actual time at the station immediately before you. That’s the shortest chain between what’s happening in operations and your decision whether to pick up the camera yet.
Common mistakes with live train tracking
- Treating the dot on the map as a measurement. It’s the result of a calculation, not an observation.
- Planning to the minute. Anyone who stands at the spot for a photo at exactly the displayed second regularly misses the shot. Buffers are essential.
- Reading missing data as a cancellation. A train that’s vanished is usually a data problem, not an operational one.
- Relying on a single source. The operator’s information, the station display and third-party maps each have different strengths – the comparison of the best train radar tools sorts that out.
- Asking the wrong source about vehicles. Class and set aren’t in timetable data. That requires observation, as the guide on current live sightings in real time describes.
- Not documenting your own experience. Anyone who notes how reliable the display is at their regular spots plans noticeably better next time.
Conclusion
Trains can be tracked live – just not in the way the word “live” suggests. What you get is a very good, timetable-based answer to “how late is this train”, and a mediocre answer to “exactly where is it”. Anyone who keeps these two levels apart gets annoyed less often by jumping dots and plans their trips far more realistically.
In practice that means: real-time information for the time question, observation for the vehicle question. How this division of labour feels in everyday use is described in the trainspotter guide to live train radar and sightings; the direct comparison between rail and road is covered in the overview of live tracking for trains and buses.
In short
Real-time data gives you a solid time report and a rough location report. For anything to do with the vehicle, you need your own observation – or that of other spotters.
Summary
- Live train tracking works through reporting points, timetable matching and forecast calculations – not through a continuous GPS trace for each train.
- The gap between what the map shows and reality grows with speed and the distance between reporting points.
- The most reliable figure is the actual time at stops; the least reliable is the interim position out on the open line.
- Anyone who really wants to know what's running combines real-time information with their own sightings and community reports.
Frequently asked questions
Can you really track trains live?
Yes, but with limitations. What's available is a continuously updated position and delay report, calculated from reports at defined points and the stored timetable. Between two reports, the system estimates where the train ought to be. It isn't a continuous live stream with second-by-second resolution like a flight radar.
How accurate is a train's live position on the map?
Accuracy depends on the distance between reporting points and on speed. On high-speed lines, the display can be several kilometres off the actual position between two reports; on dense local services it's noticeably less. The actual time at the last stop the train passed is always the more reliable figure.
Why does a train's delay display jump around?
Because the forecast is recalculated at every new reporting point. If the system receives a report that differs from the previous extrapolation, it corrects the entire remaining journey at once. From the user's point of view that looks like a jump, but it's a normal recalculation.
Can you also see freight trains in live tracking?
Not usually, in the standard passenger information systems. Those systems are built for passenger traffic. Freight traffic appears there at most indirectly, for example as the cause of a section being occupied. Anyone who wants to watch freight trains works with other sources and their own observations.
Can I see which vehicle is being used on a service?
Not from official real-time data. That describes the journey – train number, stops, times – but not the vehicle. You'll only find out the class, set or running number through sightings, whether from your own observation or reports from other spotters.
Why does a train suddenly disappear from the live display?
Typical reasons are the end of the train's run, a renumbering because of engineering works, a switch to a replacement service, or simply a missing report. A vanished dot on the map almost never means the train isn't running – only that the data chain has broken at some point.
Are live data in apps and on station displays identical?
Not necessarily. Both draw on the same underlying data, but with different update intervals and sometimes different feature sets. On the platform itself the display is usually more current, because it's closer to the operations control system and reflects platform changes sooner.
How can I check the accuracy myself?
Stand at a point with a clear view of the line, note the exact time the train passes, and compare it with what the app showed at that same moment. Repeat this over several journeys. That gives you a feel for how large the gap typically is at your location.
Read more in Train tracking & train radar
- Tracking DB Train Numbers Made Easy: The Big 2026 Guide to Real-Time Tracking of ICE, IC and RE
- Real-Time Data vs. Timetable Data: Why Every App Shows Something Different
- Tracking Freight Trains Live Made Easy: Apps, Maps, Webcams, Hotspots, Law & Safety
- Freight Train Radar Germany: Locating and Identifying Freight Trains Live
- Tracking ICE 618 Live: Position, Delay and Route in Real Time
- Tracking ICE Trains Live: The Complete Guide to Real-Time ICE Tracking
Who is behind it
Groups, brands, manufacturers and operators – who owns whom and how to recognise them out in the field.
You might also like
Live Tracking for Trains & Buses: The Best Apps, Tools & Tips for Precise Train and Bus Tracking
Maps, radar & live toolsLive Train Radar: The Best Tools and Maps Compared (2026)
Which train radar really shows live positions? An honest comparison of map tools for passenger and freight trains – including their limits and practical tips.
Maps, radar & live toolsLive Sightings Explained: How to Find Current Train Sightings in Real Time – Sources, Tools and More




