Where Does FlixBus Store Tickets and Bookings?
FlixBus keeps bookings in your account with tickets cached in a private sandbox and Wallet passes for boarding.
Last updated
FlixBus bookings live server-side. Trips, passenger details, and vouchers attach to the account. The sandbox caches tickets, QR codes, and login state.
QR codes are the boarding artifact. They render from cached bookings, so an unopened trip shows nothing at the stop. Open every leg online once, then rely on the cache or Wallet pass.
Where FlixBus stores this, by platform
/data/data/de.flixbus.app
Private sandbox for cached tickets and session. Bookings are account-side. Wallet passes cover offline boarding at signal-free stops.
/var/mobile/Containers/Data/Application/<guid>/Documents
Sandboxed container with the same account archive. Vouchers sync after login. Email confirmations backstop the app.
Frequently asked questions
Do FlixBus tickets work offline?
Tickets cache after first open, and Wallet passes work offline. Open each trip on Wi-Fi before the station, since bus stops love dead zones. Booking emails carry PDF fallback.
How do I move FlixBus bookings to a new phone?
Log in and bookings return. The sandbox held cached tickets and session that rebuild on first view. Re-add Wallet passes on the new phone.
Notice an outdated path? Let us know.