About our data

Railwise analyses publicly available timetable and real-time data from several sources, including DB Timetables APIs, GTFS and GTFS-RT. For every long-distance train, we match scheduled and reported times, platform changes and cancellations, stop by stop.

Railwise is an independent service and is not affiliated with Deutsche Bahn.

The train directory, corridor comparisons and network statistics cover ICE, IC and Flixtrain. Station boards also show other long-distance and regional services where observed. Coverage is not a complete timetable. A missing observation does not establish that a train did not run.

Punctual means arriving less than six minutes late. As in the figures Deutsche Bahn publishes, cancelled journeys are left out of punctuality, so we always show the cancellation rate beside it. Train pages judge each journey at its destination: punctuality covers journeys that arrived with a known delay, and the cancellation rate covers every journey with a known outcome, including partial cancellations. The typical delay is the median of known arrivals. The train directory, stations and the network count per stop: punctuality and mean delay use arrivals with a known delay, and the cancellation rate uses planned arrivals that were cancelled. Routes pool the arrivals at the selected destination. Early arrivals count as zero minutes late. Missing data never counts as on time or as cancelled.

In the app, many connections have a Reliability Score from 0 to 100. It summarises how dependable a connection typically is and goes beyond the standard six-minute punctuality threshold.

The score starts with historical arrival performance on the selected section. One or two minutes of delay has only a small effect, while longer delays reduce the score more heavily.

Cancellations reduce the score further. For journeys with a transfer, we also account for how often that connection has been made in the past.

As a rule of thumb, 80+ is usually very stable, 60–79 is mixed, and below 60 is noticeably riskier.

Train, station and corridor histories cover 30 completed service days. Their displayed dates identify the actual window; snapshots are rebuilt in batches and pages are cached. Live train status and station boards refresh while open. Monthly reports remain tied to their named month. Historical statistics are not predictions or a future operating calendar.

A train number can serve different routes, especially replacement services. Punctuality figures remain available for observed journeys even when routes vary: each journey is judged at its own planned destination, while the directory measures observed stops. A common historical route needs at least five usable journeys, with three quarters closely matching one actual observed route. Matching allows diversions and shortened runs: the ordered shared stops must account for at least 80% of the two stop lists combined (counting each shared stop twice), with at least three shared stops unless the lists are identical. Every variant is compared directly with the representative route, without chaining variants together. Only trains with a common route enter service rankings and route recommendations. This is a historical comparison rule, not an official timetable or replacement designation. Station aliases are grouped where the source mapping supports it.

The network overview leads with observations from the last three hours and separately shows a seven-day history. Its timestamp shows when the displayed data was computed. The cancellation chart measures cancelled observed stops.

Our data is only as complete as the railway’s real-time information. Missing or delayed reports can create gaps.

Short-notice timetable changes can cause the plan and actual operation to diverge. We show what was reported in the source data.

Railwise is provided for information only and does not replace official information from transport operators.

Despite careful processing, the displayed data may contain errors, gaps or delays. We do not guarantee that the figures are accurate, complete or current.

Before travelling, check the latest timetable directly with DB or the relevant operator.