Train regional 641Z73

Wed Unknown

It does not run today

Last recorded run: Wednesday 30 September −12 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
50%
4/8 runs under 3 min
RT coverage: 8 full · 0 partial · 0 no data
Typical delay
+5min
Median at arrival, 90 days
P90
+20min
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

  • Wed 23 Sept Max en route +44 min · last fix heading to 67354 +44 min
  • Wed 16 Sept Max en route +15 min · last fix heading to 74455 +10 min
  • Wed 19 Aug Max en route +20 min · last fix heading to 74455 +9 min
  • Wed 2 Sept Max en route +16 min · last fix heading to 74455 +8 min

Distribution · 90 days

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

  • Early 25% · 2
  • On time 25% · 2
  • 3–10 min 25% · 2
  • 10–30 min 13% · 1
  • 30+ min 13% · 1

On-time by weekday

  • — M n=0
  • — T n=0
  • 43% W n=7
  • — T n=0
  • — F n=0
  • 100% S n=1
  • — S n=0

Recent runs

DateLast stopFinalMax
Wed 30 Sept74455 21:43−12 min+9 min
Wed 23 Sept67354 21:31+44 min+44 min
Sat 19 SeptCarlisle 12:37−9 min+25 min
Wed 16 Sept74455 00:14+10 min+15 min
Wed 2 Sept74455 22:03+8 min+16 min
Wed 26 Aug74455 21:550 min+18 min
Wed 19 Aug74455 22:05+9 min+20 min
Wed 5 Aug74455 21:58+2 min+23 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.