Where Does the RMVgo App Store Tickets?
Frankfurt RMVgo keeps tickets, favorites and journey data in private storage under its Cubic package.
Last updated
RMVgo comes from Cubic for the Rhein-Main region and keeps its data in private storage under one Android package. That folder holds ticket cache, favorites and session state rather than the ticket right itself. On iOS the same app sits inside the standard per install GUID container, with the same split between local cache and account data.
Tickets stay bound to the RMV account, so inspectors see only live tickets pulled after login. After a reinstall or a phone switch, sign into the same account and re download from purchase history instead of copying folders. When departure boards look stale, clear the cache entry in system settings and reload the connection.
Where RMVgo stores this, by platform
/data/data/com.cubic.rmvgo
Private data for the verified RMVgo package. Tickets are account bound; local files hold cache and session.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for RMVgo (App Store ID 1621720603). Re login restores tickets after reinstall.
Frequently asked questions
Do RMVgo tickets survive a phone switch?
Log into the same RMV account in RMVgo on the new phone, then re download tickets from purchase history. Local folder copies never transfer validity, since inspectors check live account tickets. Keep the login current before travel so the pull works without extra steps at the platform.
Which vendor builds RMVgo?
Current RMVgo is com.cubic.rmvgo from the Rhein-Main-Verkehrsverbund. Older guides that name HaCon or eos.uptrade Frankfurt packages do not apply here, so ignore those IDs when checking Settings Apps. Quote the Cubic string when asking for help to avoid following the wrong vendor steps.
Notice an outdated path? Let us know.