Is my train on time? Check delays live in 30 seconds

Updated: August 2026 – Is my train on time? The answer is settled in under 30 seconds if you take the right route. Not the journey search, but the calling pattern via the train number. This guide first shows the quick method, then how to interpret the figures you’ll find there.

Is my train on time? The 30-second answer

To check whether your train is on time, enter the train number into the real-time journey planner, open the calling pattern for the service, and read the forecast for your stop. If there’s an actual time next to the scheduled time, you have your answer. If there’s no actual time there, no real-time data exists for that service – then the time shown is only the plan.

This route is faster and more informative than a journey search, because you see the whole service: where the delay arose, whether it’s growing, and how it develops on the way to your destination station. What the digits in a train number mean and how to find them is explained in the guide to tracking DB train numbers.

The process step by step

What the display is really telling you

Four display states get mixed up constantly. This overview sorts them out.

What you see	What it means	What you should do
Scheduled time with no actual time	No real-time data for this service	Switch to the station board or the transport association’s journey planner
Scheduled time with a matching actual time	The service is on schedule	Plan as normal, reload shortly before departure
Actual time later than scheduled	A forecast delay	Check the destination stop, work out the connection
Entry marked as cancelled	The service is cancelled	Look for an alternative and keep evidence
Entry has disappeared	Cancellation or a filter issue	Search again, reset filters, check the board
Explanatory text under the service	Additional operational information	More important than the number of minutes – always read it

Why a missing delay isn’t a good sign

The most common misconception: “There’s nothing there, so everything’s fine.” In fact, a journey planner with no real-time connection always shows the scheduled time. You’re then looking at the timetable, not reality. Why that happens and how real-time data comes about in the first place is explained in the overview of live tracking for trains and buses.

Why forecasts jump

Between two reporting points the system estimates, then the measured value replaces the estimate once it’s in. That’s why jumps of several minutes are the normal case and not an app fault. How to keep an eye on a service over the whole route is shown in the guide how to track a moving train.

Assessing a delay: growing or shrinking?

For large-scale situations, the individual service is the wrong perspective. Then it’s worth switching to line-specific disruption services such as DB Streckenagent, or checking the basic question of whether trains are running at all: Are the trains running today?

Where to find the train number

The whole process stands or falls on the number. It appears in several places, and you always have at least one of them with you.

• On the ticket or in the booking. It’s listed there for every leg of your journey, usually right next to the departure time.
• In the connection overview. Open the detail view of a connection – every service is labelled with category and number.
• On the departure board. Both the physical display and the digital version carry the number.
• On the train itself. Route boards and interior displays state the number, and long-distance trains often also show the train name.
• In the announcement. Platform announcements almost always give the category and number first.

The number’s advantage over the time is its stability: it doesn’t change through delays or platform changes. Only with splitting trains, and services that change category en route, does the designation change as scheduled – but that’s then shown in the calling pattern.

At the station: the board beats the app

If you’re already at the station, the digital departure board is often more current than your app – it’s fed directly from the operations system and frequently shows platform changes first. How to read it and what it’s missing is described in the guide to the live station departure board.

On regional services, the relevant transport association’s journey planner also often supplies finer-grained data, including bus and tram connections. An assessment of which portal is strong where is given in the overview of regional transport associations and live departures.

What applies to you at each level of delay

The practical significance of a delay depends on three things: your connection, your arrival time at the destination, and your ticket.

• Small delay with no change: no action needed, just reload shortly before departure.
• Small delay with a tight change: work out the connection and have an alternative in mind. The process is described in the guide missed connection: what to do right away.
• Larger delay on a long-distance service: check the destination stop, keep evidence, look for alternatives. Details in the guide checking current ICE delays live.
• Passenger rights: the European Passenger Rights Regulation works with tiered thresholds tied to the delay at the destination station. The specific figures, exceptions and how to claim are set out in the regulation and in the operator’s conditions of carriage – check them there for your case. This overview is not legal advice.

The difference between a forecast and proof

One point that often gets overlooked in everyday use: the forecast en route and the later proof are two different things. The forecast helps you make decisions; for anything that follows, you need the actual arrival time and evidence. That’s why it’s worth taking a screenshot with the train number visible the moment a delay becomes obvious. It costs ten seconds and can’t be done retroactively later, because the display disappears after the journey.

It’s also important to choose the right reference point. If you get off at an intermediate stop, you measure there; if you travel through, you measure at the final destination of your own journey – not at the train’s terminus. The two often differ, and that’s the most common cause of misunderstandings when sorting things out afterwards.

The check for different situations

Not every question about punctuality is the same question. These three cases need different approaches.

You’re at the station waiting

Here only the essentials count: platform, delay, explanatory text. The fastest route is this station’s departure board, not the calling pattern. Reload once more two minutes before the scheduled departure – then you have the latest status before the train pulls in.

You’re on the train with a connection ahead of you

Now the calling pattern is the right tool. Read the forecast for the connecting station, not for your final destination, and also check the connecting train. If that one’s delayed too, the problem has often solved itself before it arose.

You’re planning a trip for later

There’s no real-time data for future journeys – that only comes into being on the day of travel. What you can check is engineering works, announced replacement timetables, and whether the connection has comfortable change times at all. How to use the filters for that is shown in the power-user guide to using the DB real-time journey planner.

What to watch for in a live check

• Remember the train number, not the time. The number is stable; everything else changes.
• Always check the destination stop. The delay at departure says little about the arrival.
• Recognise a missing actual time. No value means no real-time data, not punctuality.
• Reload before every decision. An app left in the background shows an old status.
• Read the explanatory texts. They say more about how things will develop than any number of minutes.
• Trust the board at the station. It’s usually a step ahead on short-notice changes.

Conclusion

The question of punctuality is answered in 30 seconds – but only if you open the calling pattern instead of the journey search, and read the destination stop instead of your current location. Everything else is noise: jumping forecasts, changing platforms, contradictory displays. Anyone who has internalised the three steps decides more calmly and earlier than everyone else waiting on the platform for an update.