550 202
View line 550
Alerts for train 202
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line 550.
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 10 full · 0 partial · 17 no data
On-time · 90 days
83%
49/59 runs under 3 min
RT coverage: 59 full · 0 partial · 17 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: 0 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 6 Aug Max en route +8 min · last fix heading to 27 +6 min
- Wed 26 Aug Max en route +5 min · last fix heading to 27 +5 min
- Thu 3 Sept Max en route +5 min · last fix heading to 27 +5 min
- Thu 27 Aug Max en route +7 min · last fix heading to 27 +5 min
- Wed 5 Aug Max en route +7 min · last fix heading to 27 +5 min
Distribution · 90 days
59 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 8% · 5
- On time 75% · 44
- 3–10 min 17% · 10
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=9
- 100% T n=10
- 60% W n=10
- 60% T n=10
- 82% F n=11
- 100% S n=7
- 100% S n=2
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 21 Oct | capmetro-rail:5537 18:58 | No data | — |
| Tue 20 Oct | capmetro-rail:5542 19:42 | No data | — |
| Mon 19 Oct | capmetro-rail:5542 20:47 | No data | — |
| Sat 17 Oct | capmetro-rail:5542 00:48 | No data | — |
| Fri 16 Oct | capmetro-rail:5542 20:50 | No data | — |
| Thu 15 Oct | capmetro-rail:5541 21:31 | No data | — |
| Wed 14 Oct | capmetro-rail:5542 18:37 | No data | — |
| Tue 13 Oct | capmetro-rail:5542 21:42 | No data | — |
| Sun 11 Oct | capmetro-rail:5537 15:01 | No data | — |
| Sat 10 Oct | capmetro-rail:5542 00:47 | No data | — |
| Fri 9 Oct | capmetro-rail:5542 19:42 | No data | — |
| Thu 8 Oct | capmetro-rail:5536 09:55 | No data | — |
| Wed 7 Oct | capmetro-rail:5542 19:42 | No data | — |
| Tue 6 Oct | capmetro-rail:5542 19:08 | No data | — |
| Mon 5 Oct | capmetro-rail:5542 20:46 | No data | — |
| Sun 4 Oct | 5542 00:44 | No data | — |
| Sat 3 Oct | 5542 00:07 | No data | — |
| Fri 2 Oct | 5538 17:11 | 0 min | +8 min |
| Thu 1 Oct | 5542 18:39 | 0 min | +3 min |
| Wed 30 Sept | 5538 09:21 | 0 min | +1 min |
| Tue 29 Sept | 27 02:20 | −1 min | +1 min |
| Mon 28 Sept | 5542 19:10 | 0 min | +2 min |
| Sat 26 Sept | 5542 00:45 | 0 min | — |
| Fri 25 Sept | 27 02:15 | +3 min | +7 min |
| Thu 24 Sept | 5542 19:45 | 0 min | +5 min |
| Wed 23 Sept | 5541 19:59 | 0 min | +4 min |
| Tue 22 Sept | 27 02:10 | −1 min | +2 min |
| Mon 21 Sept | 5542 19:11 | 0 min | +2 min |
| Sat 19 Sept | 5542 02:33 | 0 min | — |
| Fri 18 Sept | 5541 17:03 | 0 min | +5 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 10 July 2026.