Northern 321N51

View line Northern

Mon, Tue, Wed, Thu, Fri, Sat Northern

Running now · updated 17:01

Running now 0 min

Today it is running no worse than usual: typical arrival delay is +1 min; 64% of the last 25 runs arrived on time.

On-time · 30 days
64%
16/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
64%
49/77 runs under 3 min
RT coverage: 77 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+16min
9 in 10 runs arrive with less than this
30 days: +14 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 24 Aug Max en route +59 min · last fix heading to 30040 +50 min
  • Sat 29 Aug Max en route +50 min · last fix heading to 30040 +44 min
  • Thu 27 Aug Max en route +27 min · last fix heading to 30040 +24 min
  • Wed 14 Oct Max en route +26 min · last fix heading to Layton (Lancs) +23 min
  • Fri 28 Aug Max en route +27 min · last fix heading to 30040 +23 min

Distribution · 90 days

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

  • Early 6% · 5
  • On time 57% · 44
  • 3–10 min 18% · 14
  • 10–30 min 16% · 12
  • 30+ min 3% · 2

On-time by weekday

  • 54% M n=13
  • 67% T n=12
  • 77% W n=13
  • 77% T n=13
  • 54% F n=13
  • 54% S n=13
  • — S n=0

Recent runs

DateLast stopFinalMax
Mon 2 NovChorley 16:590 min+2 min
Sat 31 OctLayton (Lancs) 17:33−1 min+17 min
Fri 30 OctPoulton-le-Fylde 17:37+3 min+8 min
Thu 29 OctLayton (Lancs) 17:340 min+5 min
Wed 28 OctLayton (Lancs) 17:43+9 min+30 min
Tue 27 OctPoulton-le-Fylde 17:33−1 min+3 min
Mon 26 OctPoulton-le-Fylde 17:52+18 min+23 min
Sat 24 OctLayton (Lancs) 17:45+11 min+14 min
Fri 23 OctPoulton-le-Fylde 17:36+2 min+7 min
Thu 22 OctLayton (Lancs) 17:49+15 min+18 min
Wed 21 OctLayton (Lancs) 17:340 min+8 min
Tue 20 OctLayton (Lancs) 17:40+6 min+12 min
Mon 19 OctLayton (Lancs) 17:33−1 min+3 min
Sat 17 OctLayton (Lancs) 17:33−1 min+9 min
Fri 16 OctPoulton-le-Fylde 17:36+2 min+8 min
Thu 15 OctPoulton-le-Fylde 17:33−1 min+4 min
Wed 14 OctLayton (Lancs) 17:57+23 min+26 min
Tue 13 OctLayton (Lancs) 17:35+1 min+5 min
Mon 12 OctLayton (Lancs) 17:40+6 min+10 min
Sat 10 OctPoulton-le-Fylde 17:46+12 min+18 min
Fri 9 OctLayton (Lancs) 17:33−1 min+5 min
Thu 8 OctLayton (Lancs) 17:33−1 min+4 min
Wed 7 OctPoulton-le-Fylde 17:34−1 min+4 min
Tue 6 OctPoulton-le-Fylde 17:33−1 min+5 min
Mon 5 OctLayton (Lancs) 17:35+1 min+4 min
Sat 3 Oct30040 17:33−1 min+18 min
Fri 2 Oct30040 17:31−3 min+3 min
Thu 1 Oct30040 17:36+2 min+4 min
Wed 30 Sept30040 17:33−1 min+7 min
Tue 29 Sept30040 17:33−1 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.