c2c 522D68
View line c2c
Alerts for train 522D68
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
22%
5/23 runs under 3 min
RT coverage: 23 full · 0 partial · 0 no data
On-time · 90 days
32%
21/66 runs under 3 min
RT coverage: 66 full · 0 partial · 0 no data
Typical delay
+6min
Median at arrival, 90 days
30 days: +7 min
P90
+12min
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
- Thu 13 Aug Max en route +20 min · last fix heading to 50499 +20 min
- Fri 14 Aug Max en route +20 min · last fix heading to 50499 +19 min
- Wed 14 Oct Max en route +16 min · last fix heading to Thorpe Bay +16 min
- Thu 8 Oct Max en route +17 min · last fix heading to Southend East +16 min
- Tue 18 Aug Max en route +17 min · last fix heading to 50499 +16 min
Distribution · 90 days
66 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 32% · 21
- 3–10 min 47% · 31
- 10–30 min 21% · 14
- 30+ min 0% · 0
On-time by weekday
- 64% M n=11
- 18% T n=11
- 18% W n=11
- 8% T n=12
- 33% F n=12
- 56% S n=9
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 17 Oct | — 00:49 | +7 min | +7 min |
| Fri 16 Oct | Thorpe Bay 20:51 | +2 min | +8 min |
| Thu 15 Oct | Thorpe Bay 20:54 | +5 min | +6 min |
| Wed 14 Oct | Thorpe Bay 21:05 | +16 min | +16 min |
| Tue 13 Oct | Thorpe Bay 20:57 | +7 min | +15 min |
| Mon 12 Oct | Southend East 20:59 | +10 min | +10 min |
| Sat 10 Oct | Pitsea 23:03 | −1 min | — |
| Fri 9 Oct | Southend East 20:56 | +7 min | +7 min |
| Thu 8 Oct | Southend East 21:06 | +16 min | +17 min |
| Wed 7 Oct | Southend East 20:57 | +8 min | +8 min |
| Mon 5 Oct | Southend East 20:51 | +2 min | +5 min |
| Sat 3 Oct | Pitsea 22:54 | +1 min | +2 min |
| Fri 2 Oct | 50499 20:51 | +2 min | +4 min |
| Thu 1 Oct | 50499 20:57 | +9 min | +9 min |
| Wed 30 Sept | 50499 20:55 | +7 min | +12 min |
| Tue 29 Sept | 50499 20:57 | +8 min | +14 min |
| Mon 28 Sept | 50499 20:55 | +6 min | +7 min |
| Sat 26 Sept | Pitsea 23:07 | +3 min | +5 min |
| Fri 25 Sept | 50499 20:53 | +4 min | +4 min |
| Thu 24 Sept | 50499 22:39 | +14 min | +18 min |
| Wed 23 Sept | 50499 21:01 | +12 min | +13 min |
| Tue 22 Sept | 50499 21:01 | +12 min | +12 min |
| Mon 21 Sept | 50499 20:58 | +9 min | +10 min |
| Fri 18 Sept | 50499 20:58 | +9 min | +9 min |
| Thu 17 Sept | 50499 20:50 | +1 min | +2 min |
| Wed 16 Sept | 50499 00:29 | +6 min | +10 min |
| Tue 15 Sept | 50499 20:58 | +10 min | +10 min |
| Mon 14 Sept | 50499 20:50 | 0 min | +1 min |
| Sat 12 Sept | Pitsea 23:03 | −1 min | — |
| Mon 7 Sept | 50499 00:27 | 0 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.