Northern 312I32

View line Northern

Mon, Tue, Wed, Thu, Fri Northern

It does not run today

Last recorded run: Friday 2 October −5 min

The mini-map returns when the train runs
On-time · 30 days
80%
8/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
On-time · 90 days
80%
8/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
Typical delay
−4min
Median at arrival, 90 days
30 days: −4 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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 21 Sept Max en route +16 min · last fix heading to 35124 +11 min
  • Thu 1 Oct Max en route +17 min · last fix heading to 35124 +3 min

Distribution · 90 days

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

  • Early 70% · 7
  • On time 10% · 1
  • 3–10 min 10% · 1
  • 10–30 min 10% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Recent runs

DateLast stopFinalMax
Fri 2 Oct35124 22:40−5 min+1 min
Thu 1 Oct35124 22:48+3 min+17 min
Wed 30 Sept35124 22:40−5 min+5 min
Tue 29 SeptDaisy Hill 22:44−1 min+8 min
Mon 28 Sept35124 22:41−4 min+8 min
Fri 25 Sept35124 22:42−3 min+8 min
Thu 24 Sept35124 22:39−7 min+5 min
Wed 23 SeptDaisy Hill 22:37−8 min+4 min
Tue 22 Sept35124 22:37−7 min—
Mon 21 Sept35124 22:56+11 min+16 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.