Asakusa 1603T
Alerts for train 1603T
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Asakusa.
Asakusa 1603T: final delay under 3 min on 16 of its 28 runs with data in the last 30 days (57%). Median final delay: +2 min. TrainsRadar data as of 22 Nov 2026, 11:49 (GMT+9).
An alert on this phone or computer when the 1603T is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Friday 20 November +3 min
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
- Mon 7 Sept Max en route +32 min · last fix heading to — +32 min
- Tue 15 Sept Max en route +13 min · last fix heading to — +13 min
- Fri 11 Sept Max en route +8 min · last fix heading to — +8 min
- Wed 28 Oct Max en route +7 min · last fix heading to Oshiage +7 min
- Fri 13 Nov Max en route +6 min · last fix heading to Oshiage +6 min
Distribution · 90 days
87 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 69% · 60
- 3–10 min 29% · 25
- 10–30 min 1% · 1
- 30+ min 1% · 1
On-time by weekday
- 50% M n=12
- 58% T n=12
- 62% W n=13
- 77% T n=13
- 38% F n=13
- 100% S n=12
- 100% S n=12
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 20 Nov | Oshiage 17:54 | +3 min | +3 min |
| Thu 19 Nov | Oshiage 17:52 | +2 min | +2 min |
| Wed 18 Nov | Oshiage 17:53 | +3 min | +3 min |
| Tue 17 Nov | Oshiage 17:53 | +3 min | +3 min |
| Mon 16 Nov | Oshiage 17:54 | +5 min | +5 min |
| Sun 15 Nov | Oshiage 17:04 | 0 min | — |
| Sat 14 Nov | Oshiage 17:04 | 0 min | — |
| Fri 13 Nov | Oshiage 17:54 | +6 min | +6 min |
| Thu 12 Nov | Oshiage 17:53 | +2 min | +2 min |
| Wed 11 Nov | Oshiage 17:49 | 0 min | — |
| Tue 10 Nov | Oshiage 17:53 | +3 min | +3 min |
| Mon 9 Nov | Oshiage 17:53 | +3 min | +3 min |
| Sun 8 Nov | Oshiage 17:04 | 0 min | — |
| Sat 7 Nov | Oshiage 17:04 | 0 min | — |
| Fri 6 Nov | Oshiage 17:54 | +3 min | +3 min |
| Thu 5 Nov | Oshiage 17:52 | +1 min | +1 min |
| Wed 4 Nov | Oshiage 17:54 | +3 min | +3 min |
| Tue 3 Nov | Oshiage 17:04 | 0 min | — |
| Mon 2 Nov | Oshiage 17:52 | +2 min | +2 min |
| Sun 1 Nov | Oshiage 17:04 | 0 min | — |
| Sat 31 Oct | Oshiage 17:04 | 0 min | +3 min |
| Fri 30 Oct | Oshiage 17:51 | +1 min | +1 min |
| Thu 29 Oct | Oshiage 17:52 | +2 min | +2 min |
| Wed 28 Oct | Oshiage 17:58 | +7 min | +7 min |
| Tue 27 Oct | Oshiage 17:53 | +3 min | +3 min |
| Mon 26 Oct | Oshiage 17:55 | +5 min | +5 min |
| Sun 25 Oct | Oshiage 17:05 | 0 min | — |
| Sat 24 Oct | Oshiage 17:04 | 0 min | — |
| Fri 23 Oct | Oshiage 17:51 | 0 min | +1 min |
| Thu 22 Oct | Oshiage 17:54 | +3 min | +3 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.