Checking bus delays live: judging your wait time realistically

Updated: August 2026 - You want to check a bus delay live and you’re faced with three numbers that contradict each other: the timetable time on the sign, the minute counter on the display, and the position on the map. This guide explains what each number means, how to work out the real state of play in about a minute, and when waiting stops being worthwhile.

Checking a bus delay live: the short answer

To check a bus delay live, you need your stop’s departure board with a live indicator - not the printed timetable. The time shown there is a prediction from the control system: it compares the trip’s reported live position against the stored scheduled timetable and projects the remaining journey time forward.

The second step is the cross-check: if a map view exists, check where the trip actually is. The prediction and the position normally line up; if they don’t, the prediction is the less reliable of the two. Why that is is explained in the article on how bus tracking works with GPS and ITCS.

Timetable time, prediction and live position compared

Most of the confusion at the stop comes from three completely different numbers looking the same. This table sorts them out.

Feature	Timetable time	Prediction (minute counter)	Live position on the map
Origin	scheduled timetable	control system’s projection	reported vehicle position
Freshness	constant	changes with every reporting point	10 to 60 seconds old
What it tells you	what should happen	what is likely to happen	where the trip is right now
Typical failure	ignores any disruption	jumps after a new update	looks frozen during a radio dead spot
Best used for	baseline planning the day before	the decision at the stop	sanity-checking the prediction
Availability	everywhere	only with real-time data	only with a published position

Which of these levels your network actually delivers is covered in the overview on bus live tracking in Germany. Without that context, you might end up looking for a map that simply doesn’t exist for your line.

Four steps to the real wait time

Typical display errors on stop displays

The dynamic display at the stop looks more official than any app - but it’s subject to the same effects. These patterns come up most often:

• The counter gets stuck on one minute. The trip is in the system, close to arrival, but isn’t reporting anything new. Usually the bus still turns up, just a little later than the display promises.
• The bus disappears from the list shortly before arrival. Often a diagram change or a sign-off in the system - not necessarily a cancellation.
• Two trips on the same line show back to back. Typical after a disruption: the delayed trip and the one scheduled right after it run together.
• The display and the app disagree. They don’t always draw on the same source and don’t always refresh at the same speed.
• The display jumps back to the timetable time. A sign that the real-time update has failed and the system has fallen back on the schedule.

Where to find the most reliable departure board for your region is covered in the guide on how to find live departures with regional transport associations.

Which source wins when in doubt

If two displays contradict each other, a simple rule helps: the source with the shorter data chain is usually more current. The display at the stop is often fed directly from the control system, giving it one fewer step than an app that goes through a published interface and has its own polling interval on top. Conversely, the app often has more context - such as disruption reports or alternative connections - that has no place on the physical display. In practice, that means: take the time from the display, the explanation from the app.

Is waiting still worth it?

The decision between waiting, walking and switching is usually made on gut feeling - and it’s often wrong, because the time already spent waiting gets factored in unconsciously. Instead, work only with what’s still ahead of you: remaining wait time plus journey time on one side, walking or an alternative connection on the other. If you’ve already waited twelve minutes, those twelve minutes are gone either way - they’re not an argument for adding another ten.

The same trade-off applies on rail, just with different figures - the comparison in the tracking guides for trains and buses shows why predictions react more sluggishly there. Long-distance coaches have their own rules again, described in the guide to Flixbus tracking with live position and delays.

How to spot a cancellation early

A cancellation almost always announces itself - you just need to know what to look out for. This order of checks has proved reliable:

• No live status right up to departure. If every other trip on the line carries a real-time indicator and yours specifically doesn’t, that’s a warning sign. It isn’t proof, though: vehicles with no registered diagram can look the same.
• The trip disappears from the list. The clearest signal. Many systems actively remove cancelled trips or mark them as dropped.
• The previous trip on the line ran badly late. Diagrams are linked: if the previous working finishes 20 minutes late, the next one starts late too - or gets cancelled to restore the interval.
• The disruption report names the line. The only really solid piece of evidence. Everything else is circumstantial.
• Other passengers are visibly waiting a long time. An unscientific but surprisingly reliable signal at busy stops.

The distinction covered in detail in the guide to bus live tracking in Germany still matters: a line that fundamentally has no real-time data will permanently look as though every trip is uncertain. So it’s worth checking once what data level your line actually has - after that, you’ll read the display quite differently.

When delays keep piling up

For a single late trip, patience is all that helps. If the same trip shows the same pattern over weeks, a different approach pays off.

• Log it factually: date, scheduled departure, actual departure, stop. After two weeks you’ll have a basis that carries more weight than any memory.
• Report it to the operator, not the transport association. The operator knows the diagram and vehicle deployment and is the only one who can actually change anything.
• Check alternative connections before getting annoyed: sometimes a parallel line or switching to the tram is simply the more robust route.
• Passenger rights on local transport are governed differently from long-distance rail, and what you’re entitled to varies with the conditions of carriage. Arbitration schemes also exist for local public transport. Whether and what you’re entitled to depends on the individual case - this is an explainer, not legal advice.

Anyone who prefers a data-driven approach to daily life simply logs the actual departure as they go. That habit helps twice over: it builds a record you can point to, and it sharpens your sense of how much typical variation there really is on your route.

Common mistakes when checking bus delays

• Using the printed timetable as a live source. It knows nothing about disruptions or delays.
• Counting the time already waited. It’s gone either way - only the remaining time matters for the decision.
• Reading a missing map icon as a cancellation. Without a report, the bus usually still runs.
• Checking only one source. The display, the app and the disruption report each have different gaps.
• Treating predictions as promises. The minute counter is a projection, recalculated at every reporting point, as the guide to real-time bus tracking explains in detail.
• Overlooking diversions. During roadworks, a bus sometimes stops at a replacement stop that doesn’t show up on the display at all - the guide on how to track a moving bus describes how to spot that.

Conclusion

Checking a bus delay live isn’t about reading off one number - it’s about bringing three pieces of information together: what was planned, what the system predicts, and where the trip actually is. Anyone who keeps these three levels apart spots cancellations earlier, gets annoyed less often by jumping displays, and makes the choice between waiting and walking with a calculation instead of a feeling.