Where Does the hvv App Store Tickets?
The hvv Hamburg app keeps mobile tickets, saved lines and favorites in private storage on Android and iOS, linked to your account.
Last updated
Hamburg Hochbahn ships the hvv app under de.eos.uptrade.android.fahrinfo.hamburg on Android. Same platform vendor as BVG, different city suffix. Tickets, alarms and saved lines live in private data. Local files hold cache and session while purchases stay account bound. Keep receipts in mail as fallback while the live ticket stays primary.
iOS containers use per install GUIDs. Quote the city name plus package when contacting support, since the vendor reuses the codebase across cities. Keep PayPal and SEPA receipts in email as backup. Log into the same account on the new phone and open My Tickets to restore. Clear cache only from system settings. Full wipe logs out and removes timetables, while favorites return after login.
Where hvv stores this, by platform
/data/data/de.eos.uptrade.android.fahrinfo.hamburg
Private data for the verified Hamburg package. Tickets are account bound; local files hold cache and session. Re login restores purchases.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the hvv iOS app. Access via backup. Same account login pulls tickets back after reinstall.
Frequently asked questions
Do hvv mobile tickets survive a phone switch?
Log into the same account on the new phone and open My Tickets. Purchases restore from the hvv backend. Local copies and screenshots are fallback only; inspectors check the live ticket.
How do I clear the hvv cache without losing tickets?
Use system app settings and clear cache only. Full storage wipe logs you out and removes downloaded timetables. Favorites return after login when synced.
Notice an outdated path? Let us know.