Using DB's Real-Time Departures Properly: Live Timetables Without Pitfalls

Updated: August 2026 – Most people use DB’s real-time departure information like a search engine: start, destination, search, done. But there’s much more behind the surface – filters that reveal connections, a running-information view that explains delays, and a clear boundary beyond which the information deliberately stays silent. This guide covers both: the tricks and the blind spots.

What DB’s real-time departure information does – and doesn’t – do

DB’s real-time departure information is Deutsche Bahn AG’s timetable service, enriched with continuously updated operational data: alongside every scheduled time comes a forecast for departure and arrival, plus platform details, cancellations and disruption texts. It covers passenger services that stop – nationwide, across all transport modes, and in several views.

What it doesn’t do matters just as much: it isn’t a vehicle-tracking service or an operations monitor. Which carriage is working a service, whether a train is running through without stopping, or whether a transfer run is currently underway – none of that is shown. This distinction explains almost every disappointment with the service. How the underlying position data actually comes about is described in the overview on live tracking of trains and buses.

The three views and what they’re good for

View	Shows you	Best suited for
Journey planner	Routes from A to B including interchanges	Trip planning, alternatives during disruptions
Departures and arrivals	All stops at a station in chronological order	Overview at the station, platform occupancy
Running information for a working	Every stop of a working with forecast	Understanding delays, following workings
Disruption notices	Text-based operational situation per route	Major incidents, engineering works, diversions

The station view is the one most often overlooked, yet it’s the most useful for anyone watching a station rather than planning a trip. Its detailed use is covered in the guide to the live station departure board.

The filters almost nobody uses

Transport-mode filter

In the advanced options you can individually enable or disable long-distance, regional, suburban rail, bus and ferry services. Two practical effects:

• Local services only shows you, during long-distance disruptions, the fallback chain via regional trains that otherwise gets buried under faster connections.
• Long-distance services only hides bus and suburban-rail walking legs when all you actually want to know is when the next long-distance train runs.

Minimum interchange time

The information calculates using stored minimum interchange times per station. Increase this value and risky connections disappear from the result – ideal for trips where you don’t want to gamble. Reduce it and you’ll see tight interchanges that you can still make with good knowledge of the station. Anyone who wants to solve the interchange question in general will find the emergency plan under missed your connection: act immediately.

Showing intermediate stops

By default the journey overview only shows the start, interchange and destination. Switch on the detailed view and you see every intermediate stop with times. For spotting this is by far the most interesting view, because from it you can work out when a working passes a particular intermediate station – even if you’re not getting on or off there.

Journeys in the past

Many information services let you set the start time retroactively. That’s useful if you want to check how a working developed yesterday, or if you regularly document the same connection. For systematic running-time research it’s also worth looking at specialised tools, as listed in the comparison of the best train radar tools.

Why non-stopping and empty workings are missing

This is the question most power users get stuck on – and it has a clear answer: passenger information is a sales and information system, not an operations system. It shows what a passenger can book and use. Everything else is deliberately excluded:

• Non-stopping passes: a train that passes through a station without stopping has no entry there. You can only find it via the working’s running information, by looking at the stops before and after.
• Empty and transfer workings: journeys without passengers exist in the operational timetable, not in the passenger information.
• Freight traffic: completely outside the system. The guide on tracking freight trains live shows how to observe it anyway.
• Special workings only appear if they’re marketed as a passenger service and entered in the timetable.

Are you already a power user of the live information?

Assessing forecast quality instead of trusting it blindly

A forecast is only as good as the data available for the route. These four questions help you weigh up a displayed minute count correctly.

For ongoing monitoring of disruption situations, the information isn’t the best tool – there are dedicated services for that, as described in the guide to the DB Streckenagent for disruptions and diversions. And if you want to know whether a single working is currently running on time, the fastest route is described in 30 seconds to a punctuality check.

Understanding the running information as a tool

The running information is the most underrated view in the whole service. It shows a working from its starting station to the end – with every stop, every scheduled time, every forecast and usually the platform too. There are four things you can read off it that appear nowhere else.

Where the train is coming from

A delay rarely originates where you’re standing. The running information shows you the point where the deviation started. If the train was already delayed when it arrived at its starting station, the cause lies in the previous rotation – such delays are persistent, because they shape the vehicle’s whole day of service.

How much buffer is still to come

Compare the arrival and departure time at each stop. Long dwell times are reserve; where there’s only a minute, there’s nothing to make up. This lets you judge for yourself whether a delay will still be present at the destination.

Roughly where the train is right now

Even without a map view you can narrow down the position: the last stop with an actual time is the last confirmed point, and the next one with a pure forecast is still ahead of the train. It’s moving somewhere in between.

When it passes a place where it doesn’t stop

For photo planning this is the real trick: from the times at the stops before and after, you can estimate the time window for any intermediate station. It will never be accurate to the minute, but it’s more than enough for a viewpoint.

Nationwide information or regional association information?

Both systems draw on partly different data pools. For long-distance travel, the nationwide information is the reference. For local transport, the regional association systems often deliver more: finer real-time data for bus and tram, connection information within the association, and disruption notices at line level. Which portal has which strengths in your region is set out in the overview of regional transport associations and live departures.

For spotting there’s a second difference: local and long-distance services follow entirely different rotation logic, which has direct consequences for planning. This connection is explained in the article local versus long-distance services compared for spotters. And if you want to keep an eye on a particular working all day, you’ll be working from the number anyway – see tracking DB train numbers.

Information for the journey, information for spotting

Both groups of users are working with the same interface, but with opposite goals. Knowing the difference means setting the filters correctly.

A practical side effect: anyone who uses the information in spotting mode understands their region’s timetable structure noticeably faster. Regular-interval hubs, crossing stations and typical rotation patterns become visible as soon as you stop searching for a single connection.

Common mistakes with the live timetable information

• Reading the forecast as fact. The figure is an extrapolation and changes with every reporting point.
• Reusing an old view. An app in the background doesn’t reliably refresh. Reload before every decision.
• Only using the journey planner. The station view answers completely different questions and is opened far too rarely.
• Assuming a cancellation from a missing entry. Trains without a stop, empty workings and freight trains never appear at all.
• Forgetting to reset filters. An active transport-mode filter from the last search distorts the next result.
• Relying on a single source. The nationwide information, the regional portal and the display at the station each have different gaps.

Verdict

DB’s real-time departure information is considerably more powerful than its default view suggests – but it’s also more clearly limited than many people think. Anyone who deliberately sets the transport-mode filter, interchange time and intermediate stops, and consistently opens the running information when there’s a delay, gets far more out of the same interface. Anything to do with vehicles rather than workings, on the other hand, belongs in other tools.