Blue 2142A
Alerts for train 2142A
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Blue.
Train 2142A: final delay under 3 min on 10 of its 10 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. TrainsRadar data as of 21 Nov 2026, 22:44 (GMT+9).
An alert on this phone or computer when the 2142A is 5 min or more late, every day it runs. No account, no email.
Running now · updated 22:43
Position estimated from the timetable
Running now 0 min
Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 10 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
Distribution · 90 days
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 17
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=1
- — W n=0
- — T n=0
- — F n=0
- 100% S n=8
- 100% S n=7
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 21 Nov | Nakagawa 22:39 | 0 min | — |
| Sun 15 Nov | Azamino 22:43 | 0 min | — |
| Sat 14 Nov | Azamino 22:43 | 0 min | — |
| Sun 8 Nov | Azamino 22:43 | 0 min | — |
| Sat 7 Nov | Azamino 22:43 | 0 min | — |
| Tue 3 Nov | Azamino 22:43 | 0 min | — |
| Sun 1 Nov | Azamino 22:43 | 0 min | — |
| Sat 31 Oct | Azamino 22:43 | 0 min | — |
| Sun 25 Oct | Azamino 22:43 | 0 min | — |
| Sat 24 Oct | Azamino 22:43 | 0 min | — |
| Sun 18 Oct | Azamino 22:43 | 0 min | — |
| Sat 17 Oct | Azamino 22:43 | 0 min | — |
| Mon 12 Oct | Azamino 22:43 | 0 min | — |
| Sun 11 Oct | Azamino 22:43 | 0 min | — |
| Sat 10 Oct | Azamino 22:43 | 0 min | — |
| Sun 4 Oct | — 22:43 | 0 min | — |
| Sat 3 Oct | — 22:43 | 0 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.