Where Does the KVB App Store Tickets?
The KVB Cologne app keeps tickets and favorites in private storage under its current ticket app package.
Last updated
Cologne uses its own ticket app rather than the HaCon builds found in Berlin and Hamburg. Current installs carry the KVB ticket package, while retired KVB mobil builds used a HanseCom ID from an earlier vendor period. Private storage on the phone holds favorites, timetable cache and session state for whichever build is installed.
Tickets themselves bind to account and device, so a raw folder copy never yields a usable ticket on another phone. After a reinstall or a device switch, log into the same KVB account and open My Tickets to pull purchases back. When departure data looks stale, clear the cache entry in system settings instead of wiping the app.
Where KVB stores this, by platform
/data/data/koeln.kvb.ticket.app
Private data for the current KVB ticket app. Retired mobil builds used a different HanseCom package. Tickets restore via account login.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for the KVB-App (App Store ID 1441639226). Access via backup. Same account restores tickets after reinstall.
Frequently asked questions
Do KVB tickets transfer to a new phone?
Log into the same KVB account on the new phone and open My Tickets. Purchases restore from the backend. The old KVB mobil package does not transfer to the new KVB-App.
Which KVB package do I have?
Current app is koeln.kvb.ticket.app. The retired KVB mobil used de.hansecom.htd.kvb.android. If guides mention an eos.uptrade Cologne package, that pattern never applied to KVB.
Notice an outdated path? Let us know.