Northern 171B13
View line Northern
Alerts for train 171B13
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Northern.
The mini-map returns when the train runs
On-time · 30 days
63%
12/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
87%
52/60 runs under 3 min
RT coverage: 60 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +7 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
- Wed 23 Sept Max en route +22 min · last fix heading to 30040 +19 min
- Fri 9 Oct Max en route +13 min · last fix heading to Bamber Bridge +13 min
- Wed 14 Oct Max en route +6 min · last fix heading to Bamber Bridge +6 min
- Wed 7 Oct Max en route +9 min · last fix heading to Poulton-le-Fylde +5 min
- Tue 29 Sept Max en route +6 min · last fix heading to 30040 +4 min
Distribution · 90 days
60 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 45% · 27
- On time 42% · 25
- 3–10 min 10% · 6
- 10–30 min 3% · 2
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 92% T n=13
- 69% W n=13
- 100% T n=13
- 85% F n=13
- 100% S n=4
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 16 Oct | Poulton-le-Fylde 08:19 | +2 min | +2 min |
| Thu 15 Oct | Poulton-le-Fylde 08:15 | −2 min | +1 min |
| Wed 14 Oct | Bamber Bridge 07:59 | +6 min | +6 min |
| Tue 13 Oct | Poulton-le-Fylde 08:19 | +2 min | +5 min |
| Mon 12 Oct | Poulton-le-Fylde 08:20 | +3 min | +5 min |
| Sat 10 Oct | Poulton-le-Fylde 08:16 | −1 min | — |
| Fri 9 Oct | Bamber Bridge 08:06 | +13 min | +13 min |
| Thu 8 Oct | Poulton-le-Fylde 08:15 | −2 min | +9 min |
| Wed 7 Oct | Poulton-le-Fylde 08:21 | +5 min | +9 min |
| Tue 6 Oct | Poulton-le-Fylde 08:16 | −1 min | +2 min |
| Fri 2 Oct | 30040 08:20 | +3 min | +5 min |
| Thu 1 Oct | 30040 08:17 | 0 min | +7 min |
| Wed 30 Sept | 30040 08:15 | −2 min | +7 min |
| Tue 29 Sept | 30040 08:21 | +4 min | +6 min |
| Fri 25 Sept | 30040 08:17 | 0 min | +4 min |
| Thu 24 Sept | 30040 08:18 | +1 min | +5 min |
| Wed 23 Sept | 30040 08:37 | +19 min | +22 min |
| Tue 22 Sept | 30040 08:15 | −2 min | +1 min |
| Fri 18 Sept | 30040 08:15 | −2 min | — |
| Thu 17 Sept | 30040 08:15 | −2 min | +4 min |
| Wed 16 Sept | 30040 08:15 | −2 min | +4 min |
| Tue 15 Sept | 30040 08:15 | −2 min | +3 min |
| Fri 11 Sept | 30040 08:15 | −2 min | +8 min |
| Thu 10 Sept | 30040 08:15 | −2 min | +1 min |
| Wed 9 Sept | 30040 08:16 | −2 min | — |
| Tue 8 Sept | 30040 08:16 | −2 min | +8 min |
| Fri 4 Sept | 30040 08:18 | +1 min | +7 min |
| Thu 3 Sept | 30040 08:17 | 0 min | +5 min |
| Wed 2 Sept | 30040 08:15 | −2 min | +1 min |
| Tue 1 Sept | 30040 08:16 | −2 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.