Train NS 2417 Rotterdam Centraal – Lelystad Centrum
It does not run today
Last recorded run: Friday 6 November No data
Next service: Monday 06:51 from Rotterdam Centraal · Mon 9 Nov
Last 30 days
Arrival delay at Lelystad Centrum, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 25 Sept Max en route +10 min · last fix heading to Amsterdam Zuid +10 min
- Thu 10 Sept Max en route +9 min · last fix heading to Amsterdam Zuid +9 min
- Wed 16 Sept Max en route +6 min · last fix heading to Amsterdam Zuid +6 min
- Thu 8 Oct Max en route +7 min · last fix heading to Almere Buiten +5 min
- Fri 21 Aug Max en route +11 min · last fix heading to Amsterdam Sloterdijk +5 min
Distribution · 90 days
50 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 16% · 8
- On time 72% · 36
- 3–10 min 12% · 6
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=9
- 100% T n=9
- 90% W n=10
- 70% T n=10
- 80% F n=10
- 100% S n=2
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 50 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 06:51 | on time | on time | |
| 07:17 / 07:18 | ≈ on time | ≈ +1 min | |
| 07:24 / 07:26 | ≈ on time | ≈ +1 min | |
| 07:30 / 07:31 | ≈ on time | ≈ +1 min | |
| 07:47 / 07:50 | ≈ on time | ≈ +2 min | |
| 07:55 | ≈ on time | ≈ +2 min | |
| 08:06 | on time | +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.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 6 Nov | Almere Buiten 08:09 | No data | — |
| Thu 5 Nov | Almere Buiten 08:09 | No data | — |
| Wed 4 Nov | Almere Buiten 08:09Partial coverage | 0 min | — |
| Tue 3 Nov | Almere Buiten 08:09Partial coverage | 0 min | — |
| Mon 2 Nov | Almere Buiten 08:09 | 0 min | — |
| Fri 30 Oct | Rotterdam Centraal 08:07 | No data | — |
| Thu 29 Oct | Almere Buiten 08:12Partial coverage | +4 min | +4 min |
| Wed 28 Oct | Almere Buiten 08:09 | 0 min | — |
| Tue 27 Oct | Almere Buiten 08:09Partial coverage | 0 min | — |
| Mon 26 Oct | Almere Buiten 08:09 | 0 min | — |
| Fri 23 Oct | Almere Buiten 08:10 | 0 min | — |
| Thu 22 Oct | Almere Buiten 08:09Partial coverage | 0 min | — |
| Wed 21 Oct | Almere Buiten 08:09Partial coverage | 0 min | — |
| Tue 20 Oct | Almere Buiten 08:10Partial coverage | +1 min | +1 min |
| Mon 19 Oct | Almere Buiten 08:09 | 0 min | — |
| Fri 16 Oct | Almere Buiten 08:10 | 0 min | — |
| Thu 15 Oct | Almere Buiten 08:10Partial coverage | 0 min | — |
| Wed 14 Oct | Almere Buiten 08:09Partial coverage | No data | — |
| Tue 13 Oct | Almere Buiten 08:24Partial coverage | 0 min | — |
| Mon 12 Oct | Almere Buiten 08:09 | 0 min | — |
| Fri 9 Oct | Almere Buiten 08:09 | 0 min | — |
| Thu 8 Oct | Almere Buiten 08:18Partial coverage | +5 min | +7 min |
| Wed 7 Oct | Almere Buiten 08:09Partial coverage | 0 min | — |
| Tue 6 Oct | Almere Buiten 08:09Partial coverage | 0 min | — |
| Mon 5 Oct | Almere Buiten 08:12 | No data | — |
| Fri 2 Oct | Duivendrecht 00:55 | −2 min | +4 min |
| Thu 1 Oct | Amsterdam Zuid 01:59 | +1 min | +9 min |
| Wed 30 Sept | Amsterdam Zuid 00:31 | −8 min | +5 min |
| Tue 29 Sept | Almere Buiten 08:09 | No data | — |
| Mon 28 Sept | Almere Buiten 08:09 | No data | — |