Transport associations in a real-time check: who really delivers live data?

Updated: August 2026 – “With real-time data” appears on almost every transport association’s website. What that actually means varies completely from region to region. This real-time check of transport associations (Verkehrsverbünde – the regional bodies that coordinate fares, timetables and passenger information in Germany) shows you which levels exist in the first place, how to recognise good data and how to assess the quality in your own region yourself within a week.

Transport associations and real-time data: the short answer

Real-time data in German public transport comes in three levels: the departure forecast at the stop, the vehicle position on a map and open access to the raw data. Nearly every association delivers level one for its core network; map views are rarer and usually limited to urban services; open, freely usable real-time interfaces are offered by considerably fewer providers.

The crucial point is this: the association doesn’t generate the data itself. It bundles what the individual transport operators feed in from their fleet management systems. That’s why quality within one and the same association area is often very uneven – excellent on urban services, patchy on the regional bus route. How the raw data is produced technically is explained in the article on real-time bus tracking.

The six criteria that decide real-time quality

Instead of a ranking that will be out of date next week, a grid helps. These six points describe what you actually notice in everyday use.

Criterion	What it means	How to recognise it	Why it matters for spotters
Forecast quality	How well the minutes shown match reality	Does it regularly differ by more than two minutes at the platform?	Determines how much buffer you need at the spot
Map view	Whether vehicle positions are displayed	Is there a map with moving symbols at all?	Only with this can you see whether a journey is already nearby
Coverage of the surrounding area	Whether regional routes deliver real-time data	Do the live markers disappear beyond the city boundary?	Decides trips away from the metropolitan areas
Disruption information	How quickly cancellations are communicated	Is the diversion in the app or only on the website?	Saves your trip when replacement services are running
Open interface	Whether data can be used for your own projects	Is there a data page with GTFS or GTFS-Realtime?	A prerequisite for your own departure boards and analyses
App usability	How quickly you get to the information	How many taps to reach a stop’s live departures?	On the platform every second counts

The association landscape: who is responsible for what

Germany has no central public transport information service, but an organically grown landscape of associations, public transport authorities and transport operators. Technically, it’s held together by the interface standards of the Association of German Transport Companies (VDV), on which practically all fleet management systems are based. Three types are relevant for data quality:

• Metropolitan associations such as VRR, HVV, MVV, VBB, RMV, VVS or VRS cover densely populated areas with many urban operators. That’s where the most capable fleet management systems are found, so forecasts and map views are usually good accordingly.
• Rural associations are responsible for large areas with many small bus companies. The timetable data is complete; real-time coverage depends on the technical equipment of each individual company.
• State-wide alliances and the nationwide data network ensure that journey information works across association boundaries. Their strength is reach; their weakness is how up to date individual details are.

In practice this means: for the question “when does something run here”, your association app is almost always the best choice. For journeys across association boundaries, you need a nationwide journey planner. And for the question of which vehicle is coming, neither of the two. The overview of regional transport associations and their live departures shows how to find your way around this landscape.

Why coverage in the surrounding area is systematically worse

This isn’t a failing of individual associations, but a chain of technical prerequisites. For a journey to deliver real-time data, five things have to be right at the same time.

If any one of these five links fails, the route is “without real-time data” for you – regardless of how well set up the association is overall. Tunnel sections add a technical world of their own, as the article on tracking underground trains in tunnels shows.

How to assess your own association in a week

Which source to use when

That third case is exactly what community sightings are for. How the two worlds work together is shown in the overview of live sightings in public transport and the comparison of apps for public transport spotters. If you’d rather process the data yourself, the overview of open rail and timetable data is the next step.

Association boundaries: the blind spot of every information service

The most unpleasant effect in the German association landscape doesn’t show up within an association, but at its edge. As soon as a journey crosses an association boundary, responsibility for the data changes – and often its quality and updating along with it.

Typical patterns you’ll observe:

• The journey breaks off in the display. The bus or train disappears from the map at the boundary even though it carries on. After that, the journey exists as a new journey in the neighbouring system.
• Two systems show different delays. Both are correct from their own point of view, because they use different reference timetables.
• The forecast jumps. At the handover point the prediction is recalculated, because the journey-time assumptions are stored differently in the neighbouring network.
• Connections aren’t protected. Connection protection usually only works within one fleet management system, not across system boundaries.

For spotters this has a welcome flip side: it’s exactly at these transitions that the exciting vehicle changes happen, because operators, vehicle types and networks meet here. If you know about the data gap, you can fill it with your own observation – and thereby supply information that isn’t in any official source.

What to watch out for

• Don’t confuse forecast with position. A number of minutes says nothing about where the vehicle is right now. The difference also becomes clear when comparing train and bus tracking.
• Expect different update intervals. Two apps on the same platform can differ by several minutes without either of them being wrong.
• Don’t expect vehicle data. No association publishes fleet numbers. If you need them, you have to document them yourself – ideally directly on your own public transport spotter map.
• Check licences before reusing data. Open access doesn’t automatically mean free use; attribution and redistribution conditions differ from dataset to dataset.
• Include off-peak times in your assessment. Late in the evening and at weekends the operator structure changes – and often the data situation with it.
• Don’t judge associations by their app alone. A weak app can sit on very good data, a slick app on a thin data basis. The two should be looked at separately.

Conclusion

The sentence “our association has real-time data” describes almost nothing. Only when you distinguish between forecast, map position and open data access, and also check the surrounding area, off-peak times and disruption communication, does a realistic picture emerge. The good news: you can build this picture yourself in a few days, and it stays valid longer than any snapshot from a comparison table. The bad news: even the best association doesn’t answer the question of which vehicle is about to come round the corner.