B804 B804
View line B804
Alerts for train B804
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line B804.
The mini-map returns when the train runs
On-time · 30 days
—
Too little data (0/1 runs with data)
RT coverage: 0 full · 0 partial · 1 no data
On-time · 90 days
—
Too little data (0/5 runs with data)
RT coverage: 0 full · 0 partial · 5 no data
Typical delay
—
Needs at least 5 runs with data (0 so far)
P90
—
Needs at least 5 runs with data (0 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
Distribution · 90 days
No runs with a known final delay yet.
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 31 Oct | — 12:09 | No data | — |
| Sun 27 Sept | — 14:59 | No data | — |
| Sat 26 Sept | — 12:09 | No data | — |
| Sun 20 Sept | — 15:29 | No data | — |
| Sat 19 Sept | — 12:34 | No data | — |
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.