Where Does the VBN App Store Tickets?
Bremen FahrPlaner tickets live in private storage under its HAFAS package, with validity restored after account login, not from copies.
Last updated
Bremen runs FahrPlaner on HAFAS tech under its own package. Private storage holds tickets cache, favorites and session. Guides copying Berlin package patterns mislead here. Tickets bind to account, so local files hold cached copies rather than validity itself. That split decides what a reinstall keeps.
Local copies never transfer validity. New phones install FahrPlaner directly and log into the same account. Tickets re download from history after login. Clearing storage while the app runs signs you out and drops cached favorites. Check purchase history inside the app when tickets look missing.
Where VBN stores this, by platform
/data/data/de.hafas.android.vbn
Private data for the verified HAFAS VBN package. Tickets restore via account; Berlin eos.uptrade pattern does not apply.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for FahrPlaner (App Store ID 478311038). Same account pulls tickets back.
Frequently asked questions
Do VBN tickets transfer phones?
Log into the same account in FahrPlaner on the new phone. Tickets re download from history. The Berlin style eos.uptrade pattern never applied to Bremen.
Which vendor builds the VBN app?
Current is de.hafas.android.vbn from the Bremen Niedersachsen transit authority, branded FahrPlaner (App Store ID 478311038). HAFAS based, not HaCon eos.uptrade.
Notice an outdated path? Let us know.