Northern 172Z04

View line Northern

Sat Northern

It does not run today

Last recorded run: Saturday 3 October −2 min

The mini-map returns when the train runs
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 12 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
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

  • Tue 29 Sept Max en route +9 min · last fix heading to 18447 +9 min

Distribution · 90 days

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

  • Early 17% · 2
  • On time 75% · 9
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Recent runs

DateLast stopFinalMax
Sat 3 Oct18447 07:18−2 min—
Fri 2 Oct18447 07:19−1 min—
Thu 1 Oct18447 07:18−1 min+3 min
Wed 30 Sept18447 07:18−1 min+3 min
Tue 29 Sept18447 07:28+9 min+9 min
Mon 28 Sept18447 07:19−1 min+1 min
Sat 26 Sept18447 07:200 min+15 min
Fri 25 Sept18447 07:200 min+1 min
Thu 24 Sept18447 07:200 min—
Wed 23 Sept18447 07:19−1 min—
Tue 22 Sept18447 07:190 min+2 min
Mon 21 Sept18447 07:18−2 min+4 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.