c2c 522R30
View line c2c
Alerts for train 522R30
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line c2c.
The mini-map returns when the train runs
On-time · 30 days
59%
16/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
On-time · 90 days
65%
55/84 runs under 3 min
RT coverage: 84 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +5 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
- Thu 20 Aug Max en route +24 min · last fix heading to 51321 +24 min
- Thu 13 Aug Max en route +24 min · last fix heading to 51321 +23 min
- Fri 14 Aug Max en route +12 min · last fix heading to 51321 +11 min
- Tue 18 Aug Max en route +10 min · last fix heading to 51321 +8 min
- Wed 16 Sept Max en route +7 min · last fix heading to 51321 +7 min
Distribution · 90 days
84 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 65% · 55
- 3–10 min 31% · 26
- 10–30 min 4% · 3
- 30+ min 0% · 0
On-time by weekday
- 85% M n=13
- 67% T n=12
- 69% W n=13
- 46% T n=13
- 58% F n=12
- 64% S n=11
- 70% S n=10
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 16 Oct | Purfleet 20:07 | 0 min | +1 min |
| Thu 15 Oct | Purfleet 20:09 | +3 min | +4 min |
| Wed 14 Oct | Purfleet 20:08 | +1 min | +1 min |
| Tue 13 Oct | Purfleet 20:07 | +1 min | +2 min |
| Mon 12 Oct | Purfleet 20:07 | 0 min | +1 min |
| Sat 10 Oct | Purfleet 13:20 | −1 min | — |
| Fri 9 Oct | Purfleet 20:11 | +5 min | +6 min |
| Thu 8 Oct | Purfleet 20:12 | +5 min | +6 min |
| Wed 7 Oct | Purfleet 20:08 | +1 min | +2 min |
| Tue 6 Oct | Purfleet 20:13 | +6 min | +7 min |
| Mon 5 Oct | Purfleet 20:07 | +1 min | +2 min |
| Sun 4 Oct | 51321 15:49 | 0 min | +1 min |
| Sat 3 Oct | 51321 13:20 | 0 min | — |
| Fri 2 Oct | 51321 20:06 | 0 min | +1 min |
| Thu 1 Oct | 51321 20:10 | +3 min | +4 min |
| Wed 30 Sept | 51321 20:09 | +3 min | +4 min |
| Tue 29 Sept | 51321 20:11 | +4 min | +4 min |
| Mon 28 Sept | 51321 20:06 | −1 min | — |
| Sat 26 Sept | 51321 13:20 | 0 min | — |
| Fri 25 Sept | 51321 20:06 | 0 min | +1 min |
| Thu 24 Sept | 51321 20:11 | +5 min | +5 min |
| Wed 23 Sept | 51321 20:06 | 0 min | — |
| Tue 22 Sept | 51321 20:07 | +1 min | +1 min |
| Mon 21 Sept | 51321 20:11 | +5 min | +5 min |
| Sun 20 Sept | Leigh-on-Sea 16:28 | +3 min | +3 min |
| Fri 18 Sept | 51321 20:11 | +5 min | +5 min |
| Thu 17 Sept | 51321 20:07 | +1 min | +2 min |
| Wed 16 Sept | 51321 20:13 | +7 min | +7 min |
| Tue 15 Sept | 51321 20:08 | +1 min | +1 min |
| Mon 14 Sept | 51321 20:14 | +7 min | +8 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.