Oedo 804B
Alerts for train 804B
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Oedo.
Oedo 804B: final delay under 3 min on 28 of its 30 runs with data in the last 30 days (93%). Median final delay: 0 min. Running now, on time. TrainsRadar data as of 22 Nov 2026, 09:33 (GMT+9).
An alert on this phone or computer when the 804B is 5 min or more late, every day it runs. No account, no email.
Running now · updated 09:33
Position estimated from the timetable
Running now 0 min
Today it is running no worse than usual: typical arrival delay is 0 min; 93% of the last 30 runs arrived on time.
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
- Thu 29 Oct Max en route +9 min · last fix heading to Hikarigaoka +8 min
- Tue 10 Nov Max en route +6 min · last fix heading to Hikarigaoka +4 min
Distribution · 90 days
90 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 98% · 88
- 3–10 min 2% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=12
- 92% T n=13
- 100% W n=13
- 92% T n=13
- 100% F n=13
- 100% S n=13
- 100% S n=13
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 22 Nov | Daimon 09:29 | 0 min | — |
| Sat 21 Nov | Hikarigaoka 10:09 | 0 min | +1 min |
| Fri 20 Nov | Hikarigaoka 10:04 | 0 min | +2 min |
| Thu 19 Nov | Hikarigaoka 10:04 | 0 min | +1 min |
| Wed 18 Nov | Hikarigaoka 10:04 | 0 min | +1 min |
| Tue 17 Nov | Hikarigaoka 10:04 | 0 min | +1 min |
| Mon 16 Nov | Hikarigaoka 10:04 | 0 min | +1 min |
| Sun 15 Nov | Hikarigaoka 10:09 | 0 min | — |
| Sat 14 Nov | Hikarigaoka 10:09 | 0 min | — |
| Fri 13 Nov | Hikarigaoka 10:05 | 0 min | +1 min |
| Thu 12 Nov | Hikarigaoka 10:07 | +2 min | +4 min |
| Wed 11 Nov | Hikarigaoka 10:04 | 0 min | +1 min |
| Tue 10 Nov | Hikarigaoka 10:09 | +4 min | +6 min |
| Mon 9 Nov | Hikarigaoka 10:04 | 0 min | +1 min |
| Sun 8 Nov | Hikarigaoka 10:09 | 0 min | +1 min |
| Sat 7 Nov | Hikarigaoka 10:09 | 0 min | +1 min |
| Fri 6 Nov | Hikarigaoka 10:04 | 0 min | +2 min |
| Thu 5 Nov | Hikarigaoka 10:04 | 0 min | +1 min |
| Wed 4 Nov | Hikarigaoka 10:04 | 0 min | +1 min |
| Tue 3 Nov | Hikarigaoka 10:09 | 0 min | +1 min |
| Mon 2 Nov | Hikarigaoka 10:04 | 0 min | — |
| Sun 1 Nov | Hikarigaoka 10:10 | 0 min | +1 min |
| Sat 31 Oct | Hikarigaoka 10:10 | 0 min | +1 min |
| Fri 30 Oct | Hikarigaoka 10:06 | 0 min | +2 min |
| Thu 29 Oct | Hikarigaoka 10:13 | +8 min | +9 min |
| Wed 28 Oct | Hikarigaoka 10:05 | 0 min | +2 min |
| Tue 27 Oct | Hikarigaoka 10:05 | 0 min | +1 min |
| Mon 26 Oct | Hikarigaoka 10:05 | 0 min | +1 min |
| Sun 25 Oct | Hikarigaoka 10:10 | 0 min | — |
| Sat 24 Oct | Hikarigaoka 10:10 | 0 min | +1 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.