Train NS 2453 Rotterdam Centraal – Lelystad Centrum

Rotterdam Centraal 15:51 → Lelystad Centrum 17:06 Daily 1 h 15 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 15:51 from Rotterdam Centraal · Fri 6 Nov

Next departure 15:51 today · Rotterdam Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 10 full · 7 partial · 12 no data
On-time · 90 days
95%
59/62 runs under 3 min
RT coverage: 52 full · 10 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +3 min

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

  • Tue 29 Sept Max en route +9 min · last fix heading to Duivendrecht +7 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Almere Buiten +4 min
  • Fri 11 Sept Max en route +7 min · last fix heading to Amsterdam Zuid +4 min

Distribution · 90 days

62 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 44% · 27
  • On time 52% · 32
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 88% T n=8
  • 89% W n=9
  • 100% T n=10
  • 88% F n=8
  • 100% S n=7
  • 100% S n=8

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 stops).

Last 90 days, 62 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.

StopSched.Usually 9 days in 10
15:51on time on time
16:17 / 16:18≈ on time ≈ +1 min
16:24 / 16:26≈ on time ≈ +1 min
16:30 / 16:31≈ on time ≈ +1 min
16:47 / 16:50≈ 1 min early ≈ +1 min
16:55≈ 1 min early ≈ +1 min
17:061 min early +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.

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

DateLast stopFinalMax
Thu 5 NovAlmere Buiten 17:14No data—
Wed 4 NovAlmere Buiten 17:34+4 min+4 min
Tue 3 NovAlmere Buiten 17:09No data—
Mon 2 NovAlmere Buiten 17:12Partial coverage0 min—
Sun 1 NovDuivendrecht 16:460 min—
Sat 31 OctDuivendrecht 16:45No data—
Fri 30 OctAlmere Buiten 17:09No data—
Thu 29 OctAlmere Buiten 17:09No data—
Wed 28 OctAlmere Buiten 17:09Partial coverage0 min—
Tue 27 OctAlmere Buiten 17:13No data—
Mon 26 OctAlmere Buiten 17:09Partial coverage0 min—
Sun 25 OctDuivendrecht 16:53No data—
Sat 24 OctAlmere Buiten 17:12+3 min+4 min
Fri 23 OctAlmere Buiten 17:10No data—
Thu 22 OctAlmere Buiten 17:14Partial coverage0 min—
Wed 21 OctAlmere Buiten 17:09No data—
Tue 20 OctAlmere Buiten 17:09No data—
Mon 19 OctAlmere Buiten 17:09Partial coverage0 min—
Sun 18 OctSchiphol Airport 16:390 min+2 min
Sat 17 OctSchiphol Airport 16:510 min—
Fri 16 OctAlmere Buiten 17:090 min—
Thu 15 OctAlmere Buiten 17:09Partial coverage0 min—
Wed 14 OctDuivendrecht 17:08No data—
Tue 13 OctAlmere Centrum 17:04No data—
Mon 12 OctAlmere Buiten 17:090 min—
Sun 11 OctDuivendrecht 16:480 min—
Sat 10 OctAlmere Buiten 17:13+2 min+5 min
Fri 9 OctAlmere Buiten 17:090 min+1 min
Thu 8 OctAlmere Buiten 17:12Partial coverage+2 min+4 min
Wed 7 OctAlmere Buiten 17:09Partial coverage0 min—