European Rail Ticket Offline Index: Can 10 Apps Show Tickets Without Data?

A train ticket can sit in an app and still depend on a connection at the wrong moment. The barcode might need an initial download. A mobile pass might require a daily online check. A ticket bought through one seller might need to be retrieved from the operating carrier. Live platform and cancellation information can require data even when the stored ticket does not.

We checked current public traveler guidance for ten European rail ticket and pass services. Four publish an explicit, scoped statement that a ticket or named ticket type can be displayed offline. Nine publish a PDF, email or print route. Four name Apple Wallet, and two name Google Wallet. Three publish screenshot guidance, but each rule has a different scope.

Study result: Save the ticket format that the seller or operator actually approves before reaching the platform. An offline timetable, a wallet button and a ticket stored in an app do not answer the same question.

The fixed panel contains Interrail and Eurail Rail Planner, Trainline, Omio, Deutsche Bahn and DB Navigator, SNCF Connect, Trenitalia, Renfe, SBB Mobile, ÖBB and Eurostar. It is a practical stratified sample, not a ranking of Europe's ten largest or most-used rail apps.

Download the complete CSV or open the source-linked JSON dataset. Each normalized row carries a SHA-256 checksum. The JSON also includes the inclusion rule, classification method, reviewed search results and ten public traveler questions that shaped the study.

Which rail ticket option fits your trip?

🏆 Where Roaming eSIM has a documented edge: One regional Roaming eSIM setup can cover the home markets of all seven operator-affiliated services in this panel. It gives a traveler one connection for ticket retrieval, app refresh, changes, rebooking and live information across supported stops, instead of arranging a separate country plan at each border. The ticket seller's presentation rule still controls what the inspector accepts.

Four of 10 services explicitly document offline ticket access

The four positive findings are not equivalent promises.

• Interrail and Eurail say Rail Planner works offline after its first connected load, but a Mobile Pass must be opened online within every 24-hour period.
• Omio says an issued mobile ticket in the purchaser's logged-in account is available offline. The booking flow can still require printing for some journeys.
• Deutsche Bahn says a linked digital BahnCard 100 and an updated subscription mobile ticket can be displayed offline. The checked material does not make that claim for every DB Navigator ticket.
• SBB says a logged-in SwissPass-linked ticket can be inspected without a connection when the traveler shows a SwissPass or official ID if requested. International partner downloads and EasyRide follow separate rules.

The other six services are recorded as not documented in the checked sources, not as no. Their pages often provide a strong local backup, but they do not make one explicit general statement that the app ticket remains displayable without data.

That distinction matters. A downloadable PDF can be an excellent offline artifact, but its existence does not prove that the app itself works without a connection. A wallet route can give quick local access, but eligibility can depend on the operator or itinerary. A page that tells a traveler to download a ticket before boarding is useful without being an explicit offline guarantee.

Backup formats are easier to verify than offline behavior

Nine services publish at least one PDF, email or print route. Interrail and Eurail Mobile Pass is the exception in this field because its current guidance requires the original pass in Rail Planner or the original paper Pass. A copied image is not an approved substitute for the Mobile Pass.

Apple Wallet is named by Trainline, SNCF Connect, SBB Mobile and Eurostar for eligible tickets. Google Wallet is named by SNCF Connect and Eurostar. Renfe uses the wording PassBook or Pass Wallet without naming a current platform, so we recorded a separate wallet route instead of assigning it to Apple or Google.

These categories overlap. SNCF Connect, for example, publishes an emailed and printable e-ticket, eligible Apple Wallet support and a separate Google Wallet route. The count does not say that every SNCF ticket qualifies for every format.

The approved artifact changes by ticket type

Trainline is the clearest example of why one service cannot always have one offline answer. Its digital ticket guide separates three products:

• An eTicket is a PDF sent by email. It can be opened on a phone, printed or added to Apple Wallet where eligible.
• A Mobile Ticket is downloaded to one device in the Trainline app and activated before travel.
• An sTicket has a dynamic barcode and is available only in the app.

The Mobile Ticket instructions explain the download and activation steps but do not state a general offline-display rule. We therefore credit the PDF and Apple Wallet paths, record the activation requirement, and leave the explicit offline field as not documented.

Trenitalia has a similar ticket-type split. Its Digital Regional Ticket validates automatically at the scheduled departure and displays a dynamic green bar. The separate Electronic Regional Ticket can be delivered as a PDF. Eligible national Frecce and Intercity ticketless journeys can use the saved PNR. Those are three different artifacts, not interchangeable backups.

Interrail's offline rule includes a 24-hour online check

Interrail's current support page says the app downloads information for offline use when it first opens with a connection. It also says a Mobile Pass must connect and be opened online at least once every 24 hours. After more than one day offline, the pass is inactive until the app reconnects.

Eurail's Rail Planner page separates offline planning from connected functions. The planner works offline, while live information and seat-reservation purchases require internet access. Pass activation also needs a connection.

This creates a simple preparation rule: do not rely on the words works offline alone. Activate the pass while connected, open it again within the required interval, and confirm that each reservation is available in the format required by the train operator.

The current Conditions of Use add a separate presentation rule. A screenshot, image, recording or copied pass layout is not accepted in place of the Mobile Pass. The device must remain powered and the display readable.

Screenshot rules cannot be generalized across rail tickets

Only three services in the panel publish screenshot-specific guidance in the checked sources, and the three instructions answer different risks.

1. Interrail and Eurail prohibit a screenshot or copy of the Mobile Pass. The original pass must be shown in Rail Planner, or the traveler must carry the original paper Pass.
2. Deutsche Bahn says products valid only as mobile-phone tickets cannot be printed or shown as a screenshot. Its PDF online tickets are a different format.
3. Eurostar advises travelers with bank cards stored on their phone not to scan a PDF or screenshot at Amsterdam Centraal ticket gates. The gate can read the payment card instead and create an accidental charge. Eurostar recommends a wallet ticket or printed ticket for that station flow.

Eurostar's instruction is not a general finding that the ticket becomes invalid. It is a station-specific scanning precaution. The Interrail and DB statements are ticket-type presentation rules. For the other seven services, no screenshot answer was found in the checked first-party traveler pages. That silence cannot be converted into permission.

Screenshot decision: Use the issued app ticket, approved PDF, wallet pass or printed ticket named by the service. Treat a screenshot as valid only when the current rule for that exact ticket says so.

What each service documents

Omio states the offline answer directly

Omio's mobile-ticket help says an issued mobile ticket is available offline in the purchaser's account. That is direct evidence, but it is not a promise that every booking produces a mobile ticket. The booking flow can say that printing is required, and the ticket remains tied to the purchasing account.

The safe sequence is to open Your Bookings before departure, verify that the correct ticket is present, and follow any print instruction attached to the booking.

Deutsche Bahn documents named offline products

Deutsche Bahn's BahnCard 100 answer says its linked digital QR code can be shown without an internet connection. Separate DB guidance distinguishes an online PDF ticket from a mobile-phone ticket. Some mobile-phone tickets are app-only and cannot be presented as a screenshot.

DB also explains how to load a ticket into the app using the booking reference and surname or a logged-in account. A missing ticket can require a refresh. These steps support a ticket-type finding, not a blanket claim about every ticket in DB Navigator.

SNCF Connect publishes several local backups

SNCF Connect's e-ticket guide says an e-ticket can be downloaded to a smartphone or printed at home or at a self-service kiosk before boarding. It is also delivered by email.

Eligible TGV INOUI, TER and Eurostar e-tickets can be added to Apple Wallet. SNCF Connect separately documents Google Wallet for e-tickets from eligible train companies except OUIGO. Adding the Google ticket requires the Wallet app, an associated Gmail account and a logged-in state at import time.

Those routes give travelers several ways to save a ticket. The checked pages do not explicitly say that the SNCF Connect app ticket remains displayable without a connection, so the offline field remains not documented.

Renfe's wallet wording does not identify a current platform

Renfe's ticket-purchasing FAQ lists printing, a mobile ticket, PassBook or Pass Wallet and the Renfe Ticket app. It does not name Apple Wallet or Google Wallet in the current English wording. We record the generic wallet route without converting it into a platform-specific score.

The checked pages also do not make a current explicit offline statement. An older corporate report mentioned offline ticket consultation, but it was excluded because it is not current traveler guidance.

SBB separates stored tickets, international downloads and EasyRide

SBB Mobile guidance says a logged-in SwissPass-linked ticket can be checked without an online connection when the traveler shows a SwissPass or official ID if requested. Its ticket overview also documents emailed PDFs and the need to download some international partner tickets before travel.

Eligible domestic tickets can be added to Apple Wallet on iPhone. SBB says Google Wallet is not currently supported and international tickets cannot currently be added to Wallet from SBB Mobile. EasyRide is a separate check-in and check-out flow that requires a continuous connection. It would be misleading to use the EasyRide rule for every stored ticket.

ÖBB's PDF rule changes at the border

The current ÖBB travel guide lists a PDF, mobile ticket and machine or counter pickup. A mobile ticket is sent to and displayed on the selected device. The guide does not explicitly say that ordinary mobile-ticket display works offline.

An ÖBB PDF can be displayed electronically within Austria, but the guide requires an A4 print for journeys to or within another country. SimplyGo follows another rule: check-in and check-out require mobile data, a brief interruption is normally tolerated, and a longer outage can force checkout.

Eurostar publishes wallet and Dutch gate guidance

Eurostar's ticket guide explains app retrieval using a booking reference and surname. Bookings without connecting journeys can be saved to Apple Wallet or Google Pay Wallet. A changed booking must be saved to the wallet again. Print-at-home and station printing are also available.

For Amsterdam Centraal, Eurostar recommends downloading the ticket close to travel and saving it to a wallet or printing it. The page explains that a phone holding bank cards can trigger the wrong reader when a PDF or screenshot is scanned at the gate. The same ticket can therefore have a presentation issue at one station even when its barcode is visible.

Why a cross-border booking can create two ticket problems

A seller, operating carrier and rail pass can each control a different artifact.

• A rail pass can prove travel entitlement while a reservation proves the seat on a specific train.
• An intermediary can sell the journey while the operating carrier controls the mobile-ticket format.
• One booking can contain separate tickets for separate operators.
• A wallet ticket can cover only the direct part of an itinerary.
• A domestic PDF rule can change when the same journey crosses a border.

This is why the study records the seller and ticket type instead of asking only whether the app works offline. Before departure, open every segment in the issued format and check that the passenger name, date, train, route and reservation are present.

If one segment is missing, a working data connection can help retrieve the booking or contact support. It cannot create a ticket that was never issued or turn an unapproved image into a valid travel document.

Prepare your rail ticket in four checks

1. Open the exact issued ticket

Do not stop at the confirmation email. Open the barcode, QR code, PDF, Mobile Pass or operator ticket that will be inspected. For a multi-operator journey, repeat the check for every segment.

2. Complete connected setup

Activate the ticket where required, import the booking, add the journey to the pass, refresh the app and sign in before leaving reliable internet. If the service publishes a reconnection interval, set a reminder before it expires.

3. Save an approved backup

Use the current first-party option for that ticket. It might be a PDF, email attachment, printout, Apple Wallet ticket, Google Wallet ticket, original paper Pass or stored app ticket. Do not invent a screenshot fallback from the appearance of a QR code.

4. Keep data for live decisions

Offline ticket display does not make delay, platform, cancellation, exchange or rebooking information available offline. Check the live journey before leaving and keep a connected option for disruption when possible.

How Roaming eSIM supports the connected part of the journey

Roaming eSIM is not scored as a rail ticket app. It solves the adjacent data problem.

The checked Europe catalog contains plans covering Austria, France, Germany, Italy, Spain, Switzerland and the United Kingdom, the home markets represented by the seven operator-affiliated services in the panel. A traveler can install before departure and use one supported regional plan across a multi-country itinerary. The public catalog exposes allowance, validity, retail price, network generation label and plan-specific top-up eligibility before checkout.

That gives Roaming eSIM three practical advantages for this decision:

• One regional setup: Keep ticket, map and messaging access across supported countries without buying a separate country plan at each border.
• Preparation before travel: Install before departure, then enable the data line after arrival.
• Visible recovery routes: My eSIMs, one-tap or QR installation, manual details, eligible-plan top-up, WhatsApp, email and 24/7 support are published on the support page.

🏆 Roaming eSIM wins the connected-recovery role: It can keep the traveler online for a pass check, missing-ticket retrieval, platform update, exchange or rebooking across supported stops. The approved PDF, wallet, printout or app pass remains the ticket backup.

Compare Roaming eSIM Europe plans before choosing the allowance and validity that fit the full itinerary. Top-up is available only on eligible plans. Coverage depends on the local partner network and is not guaranteed in tunnels, remote cuttings, stations or moving trains.

The companion European Train Wi-Fi Transparency Index compares what ten rail operators publish about onboard Wi-Fi, coverage, speeds and access rules. The Offline Maps Travel Index covers navigation without data. Together, the studies separate the ticket artifact, journey information and connection.

Questions travelers ask before relying on a rail ticket app

The ten questions below came from ten separate public Reddit discussions found during topic research. They identify practical uncertainty. They do not decide an operator's rule, so each answer follows the current first-party evidence used in the dataset.

Two patterns stand out. Travelers often treat a QR code as proof that any saved image will work, and they often treat offline planning as proof that the ticket is offline too. The current first-party instructions do not support either shortcut.

Methodology

How the 10 services were selected

The panel was fixed before classification. It contains:

• one cross-border pass system, Interrail and Eurail Rail Planner;
• two independent multi-operator intermediaries, Trainline and Omio; and
• seven operator-branded or operator-affiliated services, Deutsche Bahn and DB Navigator, SNCF Connect, Trenitalia, Renfe, SBB Mobile, ÖBB and Eurostar.

Each service has a traveler-facing app or mobile-ticket flow and a current English-language first-party consumer page that can answer at least one material field. The panel is designed to expose format differences across a realistic European itinerary. It is not weighted by users, ticket sales, routes, countries or market share.

What counted as an offline statement

A service earned the explicit offline field only when a checked current first-party traveler page said that a ticket, pass or named ticket type could be displayed without a connection. We did not infer offline access from any of the following:

• a mobile-app download button;
• the phrase stored on your phone;
• a PDF, email or print route;
• Apple Wallet or Google Wallet support;
• a Reddit report of successful use; or
• the absence of a warning.

Ticket-type support was kept narrow. A BahnCard 100 statement did not become a rule for every DB Navigator ticket. A SwissPass-linked inspection path did not become a rule for EasyRide. An issued Omio mobile ticket did not become a promise for every booking.

What was recorded for every row

The source file stores separate booleans and display text for:

1. an explicit scoped offline statement;
2. a reconnection interval;
3. activation or initial-load requirements;
4. a PDF, email or print route;
5. Apple Wallet;
6. Google Wallet;
7. another named or unnamed wallet route;
8. screenshot guidance;
9. cross-operator or route caveats;
10. live-information requirements; and
11. a first-party fallback.

The generator derives every chart and count from those booleans. It also creates the public CSV and JSON, hashes the source file and adds a checksum to every normalized row.

How search and traveler demand were used

We reviewed ten pages returned across current searches for train-ticket offline queries. Nine were single-service support or product pages. Seat61 was the only broad European rail guide in the reviewed set. None combined a fixed cross-service panel, a shared rule, row-level first-party links and a downloadable dataset.

Ten public Reddit discussions supplied distinct traveler questions about pass versus reservation QR codes, screenshots, app outages, cross-operator ticket retrieval, validation, QR generation and offline display. Reddit did not score any field. Current first-party traveler pages controlled every answer.

Study limitations

This is a documentation audit, not a test of app reliability, barcode scanning, staff behavior, account recovery or mobile reception. Public wording can lag behind an app release, and silence does not prove that a feature is absent.

The sample is intentionally mixed and not statistically representative. Ticket rules can change by seller, operator, route, fare, station and device. A field marked not documented means that the checked source set did not state it on the review date.

The study does not recommend one ticket seller or operator as the universal winner. Its purpose is to help a traveler identify the accepted ticket artifact, complete connected steps in time and preserve an approved fallback.

Reproduce or cite this study

Use the CSV dataset for analysis and the JSON dataset for the methodology, source notes, reviewed search pages and demand questions. The material is published under CC BY 4.0.

To reproduce the output:

1. Read the canonical source file at scripts/research/data/european-rail-ticket-offline-index-source.json.
2. Recheck every first-party URL and retain the ticket-type scope.
3. Run node scripts/research/generate-european-rail-ticket-offline-index.mjs.
4. Confirm that the derived totals match the CSV and article.
5. Report the review date and link to this study when quoting a finding.

Suggested citation: Roaming eSIM research team. “European Rail Ticket Offline Index: Can 10 Apps Show Tickets Without Data?” September 2026.

Editorial update policy

We will update a row when a service publishes a materially different offline, activation, wallet, screenshot or fallback rule. The historical reviewed wording remains in version control so a changed classification can be traced.

Corrections can be sent through the Roaming eSIM support page. Include the service, ticket type, public source URL and the wording that should be rechecked.