Train NS 2433 Rotterdam Centraal – Lelystad Centrum

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

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 10:51 from Rotterdam Centraal · Mon 9 Nov

Next departure 10:51 tomorrow · Rotterdam Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 9 full · 10 partial · 9 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 10 full · 13 partial · 60 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: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 23
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 23 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
10:51on time on time
11:17 / 11:18≈ on time ≈ on time
11:24 / 11:26≈ on time ≈ +1 min
11:30 / 11:31≈ on time ≈ +1 min
11:47 / 11:50≈ on time ≈ +1 min
11:55≈ on time ≈ +1 min
12:06on time +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
Fri 6 NovAlmere Buiten 12:14No data—
Thu 5 NovAlmere Buiten 12:09No data—
Wed 4 NovAlmere Buiten 12:09Partial coverage0 min+1 min
Tue 3 NovAlmere Buiten 12:24No data—
Mon 2 NovAlmere Buiten 12:09Partial coverage0 min—
Sun 1 NovDuivendrecht 11:51+1 min+1 min
Sat 31 OctAlmere Buiten 12:090 min—
Fri 30 OctAlmere Buiten 12:09No data—
Thu 29 OctAlmere Buiten 12:09Partial coverage0 min—
Wed 28 OctAlmere Buiten 12:10No data—
Tue 27 OctAlmere Centrum 12:51Partial coverage0 min—
Mon 26 OctAlmere Buiten 12:09Partial coverage0 min—
Sun 25 OctDuivendrecht 11:48No data—
Sat 24 OctAlmere Buiten 12:090 min—
Fri 23 OctAlmere Buiten 12:20No data—
Thu 22 OctAlmere Buiten 12:09Partial coverage0 min—
Wed 21 OctRotterdam Centraal 12:07No data—
Tue 20 OctAlmere Buiten 12:09Partial coverage0 min—
Mon 19 OctAlmere Buiten 12:09Partial coverage0 min—
Sun 18 OctSchiphol Airport 11:36+1 min+2 min
Sat 17 OctSchiphol Airport 11:370 min—
Fri 16 OctAlmere Buiten 12:090 min—
Thu 15 OctAlmere Buiten 12:09No data—
Wed 14 OctAlmere Buiten 12:10Partial coverage0 min—
Tue 13 OctAlmere Buiten 12:09Partial coverage0 min—
Mon 12 OctAlmere Buiten 12:090 min—
Sun 11 OctDuivendrecht 11:49+1 min—
Sat 10 OctAlmere Buiten 12:090 min—
Fri 9 OctAlmere Buiten 12:100 min—
Thu 8 OctAlmere Buiten 12:09Partial coverage0 min—