Chiltern Railways 662L40

View line Chiltern Railways

Sat Chiltern Railways

It does not run today

Last recorded run: Saturday 24 October 0 min

The mini-map returns when the train runs
On-time · 30 days
—
Too little data (2/2 runs with data)
RT coverage: 2 full · 0 partial · 0 no data
On-time · 90 days
90%
9/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

Delay at the end of each run, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 29 Aug Max en route +11 min · last fix heading to Leamington Spa +10 min

Distribution · 90 days

10 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 90% · 9
  • 3–10 min 0% · 0
  • 10–30 min 10% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 90% S n=10
  • — S n=0

Recent runs

DateLast stopFinalMax
Sat 24 OctLeamington Spa 12:150 min+1 min
Sat 3 OctLeamington Spa 12:160 min+1 min
Sat 26 SeptLeamington Spa 12:18+2 min+4 min
Sat 19 SeptLeamington Spa 12:18+2 min+3 min
Sat 12 SeptLeamington Spa 12:14−1 min+1 min
Sat 5 SeptLeamington Spa 12:16+1 min+1 min
Sat 29 AugLeamington Spa 12:26+10 min+11 min
Sat 22 AugLeamington Spa 12:17+1 min+4 min
Sat 15 AugLeamington Spa 12:14−1 min+2 min
Sat 8 AugLeamington Spa 12:15−1 min+1 min

Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.