How Does Bus Tracking Work? GPS, ITCS and Real-Time Data Explained

Updated: August 2026 – You’re standing at the stop, the app says “in 2 minutes”, and the bus suddenly reappears 400 metres further back. This guide explains how bus tracking really works – from the GPS receiver in the vehicle, through the operations control system, to the map on your phone. And above all: why the display sometimes talks nonsense.

How does bus tracking work? The short answer

Bus tracking works because every bus locates itself and reports its position. An on-board computer in the vehicle continuously determines its location via GPS, combines it with the odometer and with fixed reporting points at stops, and sends the result via mobile network to the transport company’s operations control system. There, the actual position is compared with the scheduled timetable; this difference produces the delay information, which is then passed on to apps and departure boards via a data interface.

The last step is the important one: what you see is not a raw GPS value but a processed result. That explains almost all the oddities you notice in everyday use. How to use this in practice to follow a single journey is shown in the guide on how to track a moving bus.

The three layers of bus tracking

If you want to understand why a display is wrong, you need to know in which layer the error arises. Bus tracking always consists of the same three levels.

Layer 1: The vehicle

The bus contains an on-board computer – often combined with the ticket printer, the displays inside the vehicle and the stop announcements. It knows the planned diagram, meaning which journey the vehicle is currently working, and determines the position from several sources at once:

• GNSS receiver (GPS, usually plus Galileo and GLONASS) for the absolute position
• Odometer for the distance travelled when the satellite signal is missing
• Door signals and stop reporting points, which provide a reliable reference point
• sometimes gyroscopic sensors to detect curves and changes of direction

This combination is called dead reckoning: if GPS fails, the on-board computer keeps calculating from the wheel revolutions and corrects itself at the next clean fix.

Layer 2: The operations control system (ITCS)

The reports all come together in an ITCS, the computer-aided operations control system, for whose data interfaces the Verband Deutscher Verkehrsunternehmen (Association of German Transport Companies) publishes the technical specifications. It does far more than put dots on a map:

• Scheduled-versus-actual comparison against the stored timetable → this produces the delay in minutes
• Protecting connections between lines
• Traffic-light priority at junctions
• Controlling the dynamic passenger information at stops
• Voice link to the control centre

The ITCS is the reason why a delay is often shown before the bus has even set off: the system knows that the previous working in the diagram is going to finish late.

Layer 3: The data interface

Only after that does the data become public – via standardised interfaces that transport associations and apps read. And this is where it’s decided whether you see anything at all: not every company releases real-time data for every line, and not every app evaluates all the available fields. How varied the data situation is in Germany is shown in the overview of real-time bus tracking.

Why the displayed position deviates

The most common question about bus tracking isn’t “how does it work?” but “why is it wrong?”. This table matches the typical symptoms to their real causes.

Symptom	Probable cause	What you can conclude
Bus jumps forwards or backwards	GPS fix after signal loss corrects the estimated position	Wait briefly – after the next reporting point it will be right again
Position freezes	Report fails, app stops interpolating	The bus is usually still running; the forecast becomes unreliable
Bus disappears completely	Change of diagram, fault in the on-board computer or journey without real-time release	Look at the trip number, not the map symbol
Delay suddenly jumps by 5 minutes	New forecast after a reporting point	Forecasts are projections, not measurements
Bus is shown next to the road	Position projected onto the wrong section of route	Almost always happens during diversions and engineering works
Two buses in the same place	One vehicle hasn’t logged out	The older entry usually disappears after a few minutes

How accurate is bus tracking really?

In practice, three kinds of accuracy need to be distinguished – and they are constantly confused. If you want to use this to choose your position, you’re better off working with your own bus spotter map than with the live display alone.

• Positional accuracy of the GPS fix: typically 5 to 15 metres in urban traffic, considerably worse in urban canyons.
• Positional accuracy of the display: in practice 50 to 200 metres, due to the reporting interval and interpolation.
• Time accuracy of the forecast: the only number you really care about at the stop – and it depends less on GPS than on the quality of the timetable model.

So if you want to photograph vehicles, never plan to the second. How to turn this into a reliable lead time is best worked out for yourself:

Official real-time data or community sightings?

The two sources answer different questions. Real-time data tells you when a journey is coming. Sightings tell you which vehicle is working that journey – and whether it’s worth heading out for it.

If you regularly spot buses and share sightings live, you combine both: the journey comes from the real-time information, the vehicle from the community. Incidentally, the same principle applies on the railway too, as the comparison of train and bus tracking shows.

Are you ready to make good use of bus tracking?

Common mistakes with bus tracking

• Trusting the display blindly. Between two reports, the app shows an estimate. If you plan to the second, you’re planning around an interpolation.
• Confusing the map symbol with the vehicle. A dot on the map is a journey. Which vehicle is working it isn’t shown there.
• Reading missing data as a cancellation. If a bus disappears, it’s usually still running – just without reporting.
• Taking forecasts for measurements. The minute figure is a projection by the ITCS and changes with every reporting point. With long-distance coaches this is even more pronounced, as the example of Flixbus tracking with live position and delays shows.
• Ignoring diversions. On diversion routes, the projection onto the line route is systematically wrong.
• Using only one app. The transport association’s journey planner, the transport company’s app and community data each have different gaps. Which tools are suited to what is shown in the overview of bus spotter apps.

Verdict

Bus tracking isn’t magic, nor is it a live video: it’s a chain of self-location in the vehicle, comparison in the operations control system and processing in the app. Each stage of that chain can add inaccuracy – and that’s exactly why jumps, frozen positions and buses that suddenly disappear are normal rather than broken. Once you understand this, you’ll read the display correctly: as a well-informed estimate, not a measurement.