B503 B503
View line B503
Alerts for train B503
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line B503.
It does not run today
Last recorded run: Sunday 4 October No data
The mini-map returns when the train runs
On-time · 30 days
—
Too little data (0/4 runs with data)
RT coverage: 0 full · 0 partial · 4 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 7 full · 0 partial · 6 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+2min
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
Distribution · 90 days
7 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 7
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 100% S n=7
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 4 Oct | — 11:09 | No data | — |
| Sat 3 Oct | — 09:09 | No data | — |
| Sun 27 Sept | — 13:47 | No data | — |
| Sat 26 Sept | — 07:30 | No data | — |
| Sun 13 Sept | — 11:54 | No data | — |
| Sat 12 Sept | — 05:54 | No data | — |
| Sat 5 Sept | — 12:21 | +2 min | +7 min |
| Sat 29 Aug | — 12:23 | 0 min | +7 min |
| Sat 22 Aug | — 12:24 | 0 min | +7 min |
| Sat 15 Aug | — 12:22 | +1 min | +59 min |
| Sat 8 Aug | — 12:24 | 0 min | +29 min |
| Sat 1 Aug | — 12:20 | +2 min | +4 min |
| Sat 25 Jul | — 12:21 | +2 min | +4 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.