E417 E417
Alerts for train E417
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line E417.
Train E417: final delay under 3 min on 4 of its 4 runs with data in the last 90 days (100%). TrainsRadar data as of 22 Nov 2026, 08:21 (UTC).
An alert on this phone or computer when the E417 is 5 min or more late, every day it runs. No account, no email.
Not running right now
Last recorded run: Sunday 4 October +1 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
Distribution · 90 days
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 4
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 100% S n=2
- 100% S n=2
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 4 Oct | — 16:06 | +1 min | +1 min |
| Sat 3 Oct | — 11:49 | 0 min | +3 min |
| Sun 13 Sept | — 16:07 | 0 min | +2 min |
| Sat 12 Sept | — 11:49 | 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.