Train NS 2449 Rotterdam Centraal – Lelystad Centrum

Rotterdam Centraal 14:52 → Lelystad Centrum 16:06 Daily 1 h 14 min · 7 stops NS (Nederlandse Spoorwegen)

Running now · updated 16:07

Heading to Lelystad Centrum +1 min

Estimated arrival at Lelystad Centrum 16:07 · 1 km/h

  1. Rotterdam Centraal14:52
  2. Schiphol Airport15:18
  3. Amsterdam Zuid15:25
  4. Duivendrecht15:30
  5. Almere Centrum15:47
  6. Almere Buiten15:55
  7. Lelystad Centrum16:06

Today it is running worse than usual: typical arrival delay is 0 min; 90% of the last 20 runs arrived on time.

On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 16 full · 4 partial · 8 no data
On-time · 90 days
91%
32/35 runs under 3 min
RT coverage: 29 full · 6 partial · 48 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Fri 13 Nov Max en route +13 min · last fix heading to Almere Buiten +12 min
  • Sun 18 Oct Max en route +9 min · last fix heading to Schiphol Airport +9 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Duivendrecht +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 32
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=7
  • 100% T n=4
  • 75% F n=4
  • 100% S n=4
  • 50% S n=4

Stops and timetable

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

Last 90 days, 35 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 10Today
14:52on time on time
15:18 / 15:19≈ on time ≈ +1 min
15:25 / 15:26≈ on time ≈ +1 min
15:30 / 15:31≈ on time ≈ +1 min
15:47 / 15:50≈ on time ≈ +2 min
15:55≈ on time ≈ +2 min
16:06on time +2 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 20 NovAlmere Buiten 16:04Partial coverage+1 min+1 min
Thu 19 NovAlmere Buiten 16:090 min—
Wed 18 NovAlmere Buiten 16:090 min—
Tue 17 NovAlmere Buiten 16:09+1 min+1 min
Mon 16 NovAlmere Buiten 16:53+1 min+1 min
Sun 15 NovDuivendrecht 15:44+4 min+4 min
Sat 14 NovAlmere Buiten 16:09Partial coverage0 min—
Fri 13 NovAlmere Buiten 16:29Partial coverage+12 min+13 min
Thu 12 NovAlmere Buiten 16:090 min—
Wed 11 NovAlmere Buiten 16:090 min—
Tue 10 NovAmsterdam Zuid 15:540 min+9 min
Mon 9 NovAlmere Buiten 16:090 min—
Fri 6 NovAlmere Buiten 16:09No data—
Thu 5 NovAlmere Buiten 16:09No data—
Wed 4 NovAlmere Buiten 16:12+3 min+3 min
Tue 3 NovAlmere Buiten 16:09No data—
Mon 2 NovAlmere Buiten 16:090 min—
Sun 1 NovDuivendrecht 15:470 min—
Sat 31 OctAlmere Buiten 16:09Partial coverage0 min—
Fri 30 OctAlmere Buiten 16:09No data—
Thu 29 OctAlmere Buiten 16:09No data—
Wed 28 OctAlmere Buiten 16:100 min—
Tue 27 OctAlmere Buiten 16:110 min—
Mon 26 OctAlmere Buiten 16:09No data—
Sun 25 OctDuivendrecht 15:56No data—
Sat 24 OctAlmere Buiten 16:10+1 min—
Fri 23 OctRotterdam Centraal 16:07No data—
Thu 22 OctAlmere Buiten 16:090 min—
Wed 21 OctAlmere Buiten 16:09No data—
Tue 20 OctAlmere Buiten 16:100 min—