B303 B303
View line B303
Alerts for train B303
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line B303.
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/6 runs with data)
RT coverage: 0 full · 0 partial · 6 no data
On-time · 90 days
—
Too little data (1/7 runs with data)
RT coverage: 1 full · 0 partial · 6 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 so far)
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 26 Jul Max en route +19 min · last fix heading to — +19 min
Distribution · 90 days
1 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 0% · 0
- 3–10 min 0% · 0
- 10–30 min 100% · 1
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- 0% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 4 Oct | — 11:34 | No data | — |
| Sat 3 Oct | — 06:44 | No data | — |
| Sun 27 Sept | — 14:59 | No data | — |
| Sat 26 Sept | — 09:29 | No data | — |
| Sun 20 Sept | — 15:03 | No data | — |
| Sat 19 Sept | — 10:19 | No data | — |
| Sun 26 Jul | — 10:14 | +19 min | +19 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.