Öffi, DB Navigator, Transport-Association App: Which Timetable App Wins?

Updated: August 2026 – Same connection, three apps, three different suggestions: that’s exactly the starting point for any timetable app comparison. Öffi, DB Navigator and your transport association’s app draw on similar data sources and still arrive at different results. This guide explains why that happens, which app wins in which discipline – and what spotters need on top, because none of the three shows vehicles.

Which timetable app is the best?

There’s no overall winner, but three clear discipline winners: the transport-association app is the most accurate in its own area, because it knows fare zones, engineering works and replacement services. DB Navigator wins for nationwide travel and is the only source for tickets, reservations and passenger rights. Öffi is the fastest when you just want to know what’s leaving your stop in the next few minutes.

The key point for all three: they show trips, not vehicles. If you want to know which carriage is coming, you need a fourth source – the community. The guide to real-time bus tracking describes what the technical chain behind that looks like.

Why the same connection looks different

When three apps make different suggestions, it’s rarely down to the timetable data. It’s down to the rules they use to assemble connections.

• Minimum transfer time: some apps calculate generously, others suggest tight transfers. That changes the whole journey chain.
• Assessment of walking distances: how quickly does the app assume you can walk between two stops? There are significant differences here.
• Mode-of-transport preference: does the app favour rail, or suggest the bus if it’s nominally faster?
• Handling of real-time data: is a connection recalculated on a delay, or just flagged with minus minutes?
• Fare knowledge: transport-association apps know zones and special rules, nationwide apps often only the broad framework.

The data source is rarely the problem

Real-time data comes from the transport companies’ operations control systems and is provided via standardised interfaces. An app can retrieve this data at different frequencies and present it differently – but it can’t invent data that hasn’t been released. Where these releases stand regionally is shown in the overview of regional transport associations and their live departures.

The direct comparison

Criterion	Öffi	DB Navigator	Regional association app	Spotting app
Departure board per stop	very fast and clear	present	present, often with extra info	no
Real-time quality in local traffic	good, depends on the network	good, nationwide	usually the most accurate	not relevant
Transfer logic across association boundaries	solid	core strength	usually ends at the boundary	no
Ticket purchase and reservation	no	the only comprehensive source	for its own region	no
Accessibility information	depends on data availability	present	often the most up to date	no
Offline use	partial	limited	partial	own data, yes
Vehicle type and wagon number	no	no	no	core function
Typical use case	quick departure info	travel and tickets	everyday use within an association	spotting and documentation

Which timetable app suits your everyday life?

The three candidates in brief

Öffi

Öffi is a lean information tool with no sales features. Its strength lies in fast departure boards: choose a stop, see the departures, done. It integrates data from many transport associations, which makes it especially interesting for people who frequently switch between networks. You can’t buy tickets with it, and coverage – as everywhere – depends on which interfaces are available in the relevant area. So check first whether your association works cleanly within it.

DB Navigator

The official app covers the widest range of features: nationwide connection search, real-time forecasts, platform information, ticket purchase, reservation, and handling passenger rights. For local-traffic questions within an association it’s usable, but not always as detailed as the local app – especially for fare-related special cases and short-notice service changes. The comparison DB Navigator versus tracking apps describes where its limits lie for railway fans.

Your transport association’s app

It’s the specialist: fare zones, short-trip rules, engineering-works information, replacement services and local ticket products are most up to date here. The price for that is the boundary – beyond the association’s area, its expertise usually ends. For people who travel the same routes every day, though, it’s still usually the best starting page.

The spotter’s view: what all three apps lack

For public transport spotters, the comparison is sobering: none of the three apps answers the actual question. They tell you that a service on line 4 is coming at 2:12 pm – but not whether it’s the older vehicle with the special livery you’ve been waiting weeks for.

This information only comes from observation. That’s why spotters work with a combination: a timetable app for the time, a spotting app for the vehicle. How that builds up into a reliable overview of a fleet over months is described in the guide to the app for public transport spotters; a broader tool overview is in the comparison of public transport spotting apps.

For live observation in local traffic, the guide public transport spotting live is the right complement; specifically for trams, see the guide on how to track a moving tram.

How to test three apps on the same connection

A comparison is only meaningful if all the apps get the same task. This process takes a quarter of an hour and gives you a result for your own region – not for some model city.

Anyone who regularly observes vehicles adds a sixth point: how quickly can I get from the departure display to logging my sighting? That’s exactly where timetable apps and spotting tools finally part ways – which is why most public transport fans end up with both on their home screen.

What to look out for when testing

• Check your actual route, not the sample connection. An app can be brilliant in Berlin and blind in your county town.
• Compare at peak time. Differences in real-time quality show up when delays actually occur.
• Watch for honest labelling. Good apps say when no real-time data is available. Poor ones show scheduled times without comment.
• Test a transfer with little buffer. That immediately shows you how conservatively the transfer logic calculates.
• Look at behaviour during disruptions. Is an alternative suggested, or does the broken connection just stay there?
• Think about battery and data usage. Constantly open maps cost noticeably – how much is shown in the guide to data usage and battery in live tracking.

Conclusion

The timetable app comparison doesn’t end with a single winner, but with a division of roles. The transport-association app wins in everyday life because it knows the local quirks. The nationwide app wins on travel because it ignores boundaries and includes the ticket. A lean departure board wins in the situation where you just want to know if you still need to run. And for anything to do with vehicles, none of these apps is responsible anyway – that’s what the spotting community is for, as the comparison of trainspotting apps also shows.