SC 100502 100502
View line SC 100502
Alerts for train 100502
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line SC 100502.
It does not run today
Last recorded run: Sunday 4 October −5 min
The mini-map returns when the train runs
On-time · 30 days
33%
1/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
17%
1/6 runs under 3 min
RT coverage: 6 full · 0 partial · 0 no data
Typical delay
+10min
Median at arrival, 90 days
P90
+31min
9 in 10 runs arrive with less than this
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
- Sun 19 Jul Max en route +49 min · last fix heading to — +49 min
- Sun 26 Jul Max en route +12 min · last fix heading to — +12 min
- Sun 20 Sept Max en route +13 min · last fix heading to — +11 min
- Mon 28 Sept Max en route +16 min · last fix heading to — +9 min
- Sun 2 Aug Max en route +6 min · last fix heading to — +6 min
Distribution · 90 days
6 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 17% · 1
- On time 0% · 0
- 3–10 min 33% · 2
- 10–30 min 33% · 2
- 30+ min 17% · 1
On-time by weekday
- 0% M n=1
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- 20% S n=5
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 4 Oct | — 19:33 | −5 min | +4 min |
| Mon 28 Sept | — 19:49 | +9 min | +16 min |
| Sun 20 Sept | — 17:23 | +11 min | +13 min |
| Sun 2 Aug | — 19:44 | +6 min | +6 min |
| Sun 26 Jul | — 19:54 | +12 min | +12 min |
| Sun 19 Jul | — 20:29 | +49 min | +49 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.