Chiltern Railways 632B70

View line Chiltern Railways

Mon, Sun Chiltern Railways

It does not run today

Last recorded run: Sunday 4 October +2 min

The mini-map returns when the train runs
On-time · 30 days
75%
3/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
78%
7/9 runs under 3 min
RT coverage: 9 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

  • Sun 27 Sept Max en route +5 min · last fix heading to Aylesbury +4 min
  • Sun 9 Aug Max en route +5 min · last fix heading to Aylesbury +3 min

Distribution · 90 days

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

  • Early 11% · 1
  • On time 67% · 6
  • 3–10 min 22% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • 71% S n=7

Recent runs

DateLast stopFinalMax
Sun 4 OctAylesbury 23:44+2 min+4 min
Sun 27 SeptAylesbury 00:10+4 min+5 min
Mon 14 Sept— 09:160 min—
Sun 13 SeptAylesbury Vale Parkway 23:24−2 min+2 min
Mon 31 Aug— 04:39+1 min+1 min
Sun 30 AugAylesbury 23:340 min+2 min
Sun 23 AugAylesbury 00:540 min—
Sun 9 AugAylesbury 23:38+3 min+5 min
Sun 26 JulAylesbury 00:49+1 min+2 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.