Northern 182Z27

View line Northern

Mon, Tue, Wed, Thu, Fri, 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
91%
10/11 runs under 3 min
RT coverage: 11 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
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

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

  • Mon 28 Sept Max en route +9 min · last fix heading to 17135 +6 min

Distribution · 90 days

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

  • Early 42% · 5
  • On time 50% · 6
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Recent runs

DateLast stopFinalMax
Sat 3 Oct17135 21:11−2 min+3 min
Fri 2 Oct17135 21:160 min+4 min
Wed 30 Sept17135 21:14−2 min—
Tue 29 Sept17135 21:160 min—
Mon 28 Sept17135 21:23+6 min+9 min
Sat 26 Sept17135 21:14+2 min+3 min
Fri 25 Sept17135 21:15−3 min—
Thu 24 Sept17135 21:18+2 min+2 min
Wed 23 Sept17135 21:14−3 min—
Tue 22 Sept17135 21:14−2 min—
Mon 21 Sept17135 21:170 min+6 min
Sat 25 Jul17135 21:10+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.