Where Does DB Navigator Store Tickets and Bookings?
DB Navigator keeps tickets and bookings in your Bahn account with the phone holding a private cache and offline tickets.
Last updated
DB Navigator is account-backed. Timetables come from the server while tickets, BahnCards, and Deutschland-Tickets attach to your login. The sandbox holds cached trips, PDFs, and login session.
That is why reinstalls feel painless after login. Active tickets reappear and the comfort check-in state restores. Keep the app updated around timetable changes, since cached connections go stale fast.
Where DB Navigator stores this, by platform
/data/data/de.hafas.android.db
Private sandbox for ticket cache and session. Bookings sync from the Bahn account. Open each ticket online once so it caches for offline gates.
/var/mobile/Containers/Data/Application/<guid>/Documents
Sandboxed container with the same account archive. Wallet passes duplicate the ticket outside the app. Watch app mirrors from the phone install.
Frequently asked questions
Are DB Navigator tickets available offline?
Open the ticket in My Trips while online once. It caches for offline inspection checks. Screenshots work as a fallback but the in-app ticket with live status is what conductors scan.
How do I move DB Navigator to a new phone?
Log in on the new phone. Bookings and BahnBonus sync from the account. Saved travelers and payment methods come along. Only the local cache rebuilds.
Notice an outdated path? Let us know.