P321 P321 M3 Parkway – Docklands
Alerts for train P321
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line P321.
It has not run yet today
Last recorded run: Thursday 5 November 0 min
Next service: today 16:40 from M3 Parkway · Fri 6 Nov
Last 30 days
Arrival delay at Docklands, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 29 Oct Max en route +16 min · last fix heading to — +14 min
- Fri 30 Oct Max en route +14 min · last fix heading to — +11 min
- Thu 13 Aug Max en route +12 min · last fix heading to — +10 min
- Tue 8 Sept Max en route +10 min · last fix heading to — +7 min
- Thu 15 Oct Max en route +3 min · last fix heading to — +3 min
Distribution · 90 days
62 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 85% · 53
- 3–10 min 10% · 6
- 10–30 min 5% · 3
- 30+ min 0% · 0
On-time by weekday
- 92% M n=12
- 85% T n=13
- 92% W n=13
- 69% T n=13
- 91% F n=11
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 62 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 16:40 | +1 min | +2 min | |
| 16:43 | ≈ +1 min | ≈ +2 min | |
| 16:47 / 16:48 | ≈ +1 min | ≈ +2 min | |
| 16:51 / 16:52 | ≈ +1 min | ≈ +2 min | |
| 17:02 / 17:03 | ≈ +1 min | ≈ +2 min | |
| 17:12 | +1 min | +3 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.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 5 Nov | — 17:09 | 0 min | — |
| Wed 4 Nov | — 17:09 | +1 min | +3 min |
| Tue 3 Nov | — 17:09 | 0 min | +1 min |
| Mon 2 Nov | — 17:09 | 0 min | +1 min |
| Fri 30 Oct | — 17:33 | +11 min | +14 min |
| Thu 29 Oct | — 17:35 | +14 min | +16 min |
| Wed 28 Oct | — 17:20 | +1 min | +1 min |
| Tue 27 Oct | — 17:20 | +1 min | +1 min |
| Fri 23 Oct | — 17:21 | 0 min | +3 min |
| Thu 22 Oct | — 17:19 | +2 min | +2 min |
| Wed 21 Oct | — 17:20 | +1 min | +2 min |
| Tue 20 Oct | — 17:19 | +2 min | +2 min |
| Mon 19 Oct | — 17:20 | +1 min | +1 min |
| Fri 16 Oct | — 17:20 | 0 min | +1 min |
| Thu 15 Oct | — 17:17 | +3 min | +3 min |
| Wed 14 Oct | — 17:20 | +1 min | +2 min |
| Tue 13 Oct | — 17:19 | +2 min | +2 min |
| Mon 12 Oct | — 17:20 | +1 min | +1 min |
| Fri 9 Oct | — 17:19 | +2 min | +2 min |
| Thu 8 Oct | — 17:19 | +1 min | +4 min |
| Wed 7 Oct | — 17:21 | 0 min | +1 min |
| Tue 6 Oct | — 17:19 | +2 min | +2 min |
| Mon 5 Oct | — 17:19 | +2 min | +2 min |
| Fri 2 Oct | — 17:20 | 0 min | +1 min |
| Thu 1 Oct | — 17:19 | +2 min | +2 min |
| Wed 30 Sept | — 17:20 | +1 min | +1 min |
| Tue 29 Sept | — 17:20 | +1 min | +1 min |
| Mon 28 Sept | — 17:20 | +1 min | +2 min |
| Thu 24 Sept | — 17:20 | 0 min | +1 min |
| Wed 23 Sept | — 17:18 | +3 min | +3 min |