How We Calculate

Where the Data Comes From

Railhop works only from licensed and official sources. It never guesses a train's times.

• Live and recorded train running: National Rail Enquiries' Darwin feed (Powered by National Rail Enquiries), recorded by Railhop for every passenger train in Great Britain since 2 October 2026.
• The timetable and planned cancellations: Network Rail's timetable. Contains information of Network Rail Infrastructure Limited. Where the Darwin feed missed a train, the same train's times from Network Rail's train movements are used.
• September 2026 and older journeys: National Rail's Historical Service Performance (HSP) records, published by Rail Delivery Group on the Rail Data Marketplace.
• Fares: the Rail Settlement Plan fares data (Price from National Rail Enquiries / Rail Settlement Plan data), loaded every week.
• Each train company's Delay Repay rules: its own Delay Repay page and Conditions of Travel. Each guide shows the day they were last checked.

How a Delay Is Worked Out

A delay is measured where Delay Repay measures it: at your destination station. It is the train's actual arrival there against the public timetable's arrival, in whole minutes counted down, so 29 minutes 30 seconds is 29 minutes.

A train retimed on the day is measured from the time you planned for, its original time. The actual arrival comes from the live feed first, then Network Rail's train movements, then HSP. If none of them has an actual time, Railhop says so and waits; it never fills in an estimate.

How the Share of Trains Late Enough to Claim Is Worked Out

The monthly Delay Repay report counts a train as late enough to claim when it reached its final stop at least as late as its company's own Delay Repay threshold (15, 30 or 60 minutes), or didn't complete the journey: cancelled, cut short, or its first stop cancelled. That is what a passenger travelling the whole way could claim for.

The share is those trains divided by every train whose outcome is known. Trains cancelled in the timetable by 22:00 the evening before are left out, because Delay Repay doesn't pay for them, and so are trains whose outcome isn't known. Replacement buses are not counted.

Before a month is published it is checked: at least 28 days, every day final, nearly every train's outcome known, no long gaps in the feed, and no figure that jumps without a reason. A month that fails a check is held back, not published.

Station and Disruption Figures

A station page's delay history counts every train that called there with a live time over the last 30 and 90 days, to the day before. A train is late at a station when it arrived there 15 minutes or more after its planned time, measured as a journey from where the train started. Cancelled calls are stops cancelled on the day. The figures are rebuilt every night.

A disruption page is made when National Rail reports a problem and Railhop's own train data shows it mattered: the line blocked or closed, 4 or more trains cancelled or cut short, or, on a stretch with at least 6 trains due, 3 or more trains 30 minutes late or 4 or more cancelled or late. It is updated every few minutes for 24 hours.

How Fares and Amounts Owed Are Worked Out

What you're owed is the band your delay falls in, as a share of your ticket price, using the train company's own bands. For most companies a delay of 15 minutes pays 25% of a Single, 30 minutes 50%, and 60 minutes or more 100%; a Return pays half of those shares of the Return price, and the whole Return from 120 minutes. Companies on Delay Repay 30 start at 30 minutes, and a few have their own rules.

For a Season Ticket, the price you paid is divided by the journeys it covers (for example 10 for a Weekly and 464 for an Annual), then the band's share is applied. Where a company doesn't publish its method, the amount is marked as an estimate, and where two sources disagree the lower amount is used.

When Railhop suggests a fare, it uses only walk-up fares (Anytime and Off-Peak Singles and Returns, standard class) that are valid for the train: the ticket's route must allow it (Any Permitted, a named company's trains only, via or not via a station), and Off-Peak restrictions are checked against the day and time. Advance fares are never guessed, and no amount is shown without a ticket price.

What the Figures Can't Tell You

"Late enough to claim" is Railhop's estimate for a passenger travelling to the train's final stop, so your own journey may differ. The train company decides every claim.

These figures are not ORR's official punctuality statistics, which measure trains against the timetable at each station. September 2026 comes from HSP, which estimates cancellations from a sample and can't tell planned cancellations apart. The live feed carries only part of the Elizabeth line's and London Overground's timetables, and their figures cover the trains it carries.

How Often the Figures Change

• Station and disruption pages: live, refreshed every minute to every few minutes.
• Station delay history: rebuilt every night.
• The Delay Repay report: a new month on the 1st, once it passes its checks.
• Fares: every week.
• Train companies' rules: checked against their own pages; each guide shows the date.

Corrections

If something doesn't match a train company's own page, the train company's page is right. Tell us through the contact form or at hello@railhop.app and we'll check it, fix it and update the page's date. Figures are provided as they are and may contain errors.

Railhop is independent and isn't endorsed by Rail Delivery Group, National Rail, Network Rail or any train company.