Train NS 2453 Rotterdam Centraal – Lelystad Centrum
It has not run yet today
Last recorded run: Friday 20 November +1 min
Next service: today 15:52 from Rotterdam Centraal · Sat 21 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
- Sat 14 Nov Max en route +29 min · last fix heading to Almere Buiten +29 min
- Wed 18 Nov Max en route +9 min · last fix heading to Almere Buiten +9 min
- Tue 17 Nov Max en route +7 min · last fix heading to Almere Buiten +7 min
- Tue 29 Sept Max en route +9 min · last fix heading to Duivendrecht +7 min
- Mon 9 Nov Max en route +6 min · last fix heading to Almere Buiten +5 min
Distribution · 90 days
66 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 32% · 21
- On time 58% · 38
- 3–10 min 9% · 6
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 92% M n=13
- 78% T n=9
- 80% W n=10
- 100% T n=11
- 90% F n=10
- 83% S n=6
- 100% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 67 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 |
|---|---|---|---|
| 15:52 | on time | on time | |
| 16:18 / 16:19 | ≈ on time | ≈ +1 min | |
| 16:25 / 16:26 | ≈ on time | ≈ +2 min | |
| 16:30 / 16:31 | ≈ on time | ≈ +2 min | |
| 16:47 / 16:50 | ≈ on time | ≈ +2 min | |
| 16:55 | ≈ on time | ≈ +2 min | |
| 17: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 20 Nov | Almere Buiten 17:09Partial coverage | +1 min | +1 min |
| Thu 19 Nov | Almere Buiten 17:09 | 0 min | — |
| Wed 18 Nov | Almere Buiten 17:24 | +9 min | +9 min |
| Tue 17 Nov | Almere Buiten 17:09 | +7 min | +7 min |
| Mon 16 Nov | Almere Buiten 17:09 | 0 min | — |
| Sun 15 Nov | Duivendrecht 16:49 | +1 min | +1 min |
| Sat 14 Nov | Almere Buiten 17:29Partial coverage | +29 min | +29 min |
| Fri 13 Nov | Almere Buiten 17:09Partial coverage | 0 min | — |
| Thu 12 Nov | Almere Buiten 17:09 | +2 min | +2 min |
| Wed 11 Nov | Almere Buiten 17:12 | +3 min | +3 min |
| Tue 10 Nov | Amsterdam Zuid 16:39 | 0 min | — |
| Mon 9 Nov | Almere Buiten 17:18 | +5 min | +6 min |
| Fri 6 Nov | Rotterdam Centraal 16:49 | No data | — |
| Thu 5 Nov | Almere Buiten 17:14 | No data | — |
| Wed 4 Nov | Almere Buiten 17:34 | +4 min | +4 min |
| Tue 3 Nov | Almere Buiten 17:09 | No data | — |
| Mon 2 Nov | Almere Buiten 17:12 | 0 min | — |
| Sun 1 Nov | Duivendrecht 16:46 | 0 min | — |
| Sat 31 Oct | Duivendrecht 16:45Partial coverage | No data | — |
| Fri 30 Oct | Almere Buiten 17:09 | No data | — |
| Thu 29 Oct | Almere Buiten 17:09 | No data | — |
| Wed 28 Oct | Almere Buiten 17:09 | 0 min | — |
| Tue 27 Oct | Almere Buiten 17:13 | No data | — |
| Mon 26 Oct | Almere Buiten 17:09 | 0 min | — |
| Sun 25 Oct | Duivendrecht 16:53 | No data | — |
| Sat 24 Oct | Almere Buiten 17:12 | +3 min | +4 min |
| Fri 23 Oct | Almere Buiten 17:10 | No data | — |
| Thu 22 Oct | Almere Buiten 17:14 | 0 min | — |
| Wed 21 Oct | Almere Buiten 17:09 | No data | — |
| Tue 20 Oct | Almere Buiten 17:09 | No data | — |