550 102
View line 550
Alerts for train 102
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.
It does not run today
Last recorded run: Friday 16 October +1 min
The mini-map returns when the train runs
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 12 full · 0 partial · 12 no data
On-time · 90 days
78%
43/55 runs under 3 min
RT coverage: 55 full · 0 partial · 12 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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
- Tue 18 Aug Max en route +16 min · last fix heading to 27 +10 min
- Mon 27 Jul Max en route +12 min · last fix heading to 27 +7 min
- Wed 9 Sept Max en route +11 min · last fix heading to 27 +7 min
- Thu 30 Jul Max en route +8 min · last fix heading to 27 +6 min
- Thu 15 Oct Max en route +7 min · last fix heading to capmetro-rail:5542 +6 min
Distribution · 90 days
55 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 20% · 11
- On time 58% · 32
- 3–10 min 20% · 11
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 78% M n=9
- 80% T n=10
- 70% W n=10
- 64% T n=11
- 92% F n=12
- 100% S n=3
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 16 Oct | capmetro-rail:5542 01:53 | +1 min | +5 min |
| Thu 15 Oct | capmetro-rail:5542 20:13 | +6 min | +7 min |
| Wed 14 Oct | capmetro-rail:5542 20:16 | No data | — |
| Tue 13 Oct | capmetro-rail:5542 19:07 | No data | — |
| Mon 12 Oct | capmetro-rail:5542 20:47 | No data | — |
| Sun 11 Oct | capmetro-rail:5542 02:32 | No data | — |
| Sat 10 Oct | capmetro-rail:5542 02:33 | No data | — |
| Fri 9 Oct | capmetro-rail:5542 18:33 | No data | — |
| Thu 8 Oct | capmetro-rail:5542 20:16 | No data | — |
| Wed 7 Oct | capmetro-rail:5542 20:15 | No data | — |
| Tue 6 Oct | capmetro-rail:5542 19:43 | No data | — |
| Mon 5 Oct | capmetro-rail:5542 19:07 | No data | — |
| Sun 4 Oct | 5542 01:56 | No data | — |
| Sat 3 Oct | 5542 00:45 | No data | — |
| Fri 2 Oct | 5535 17:11 | 0 min | +6 min |
| Thu 1 Oct | 5538 19:23 | 0 min | +5 min |
| Wed 30 Sept | 27 02:36 | +2 min | +4 min |
| Tue 29 Sept | 5542 19:53 | 0 min | +7 min |
| Mon 28 Sept | 5542 19:08 | 0 min | +7 min |
| Sat 26 Sept | 5542 01:57 | 0 min | — |
| Fri 25 Sept | 5542 19:59 | 0 min | +6 min |
| Thu 24 Sept | 8 03:52 | +4 min | +5 min |
| Wed 23 Sept | 5542 19:42 | 0 min | +5 min |
| Tue 22 Sept | 5537 19:59 | 0 min | +6 min |
| Mon 21 Sept | 5542 19:09 | 0 min | +8 min |
| Sat 19 Sept | 5542 00:43 | 0 min | — |
| Fri 18 Sept | 5536 17:03 | 0 min | +6 min |
| Thu 17 Sept | 5542 19:11 | 0 min | +4 min |
| Wed 16 Sept | 27 02:35 | +1 min | +5 min |
| Tue 15 Sept | 5539 11:21 | 0 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.