Train NS 2429 Rotterdam Centraal – Lelystad Centrum

Rotterdam Centraal 09:54 → Lelystad Centrum 11:06 Daily 1 h 12 min · 7 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Almere Buiten at 11:36 No data

  1. Rotterdam Centraal09:54
  2. Schiphol Airport10:20
  3. Amsterdam Zuid10:27
  4. Duivendrecht10:34
  5. Almere Centrum10:49
  6. Almere Buiten10:55
  7. Lelystad Centrum11:06

Next service: tomorrow 09:54 from Rotterdam Centraal · Wed 28 Oct

Next departure 09:54 tomorrow · Rotterdam Centraal
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 19 full · 1 partial · 10 no data
On-time · 90 days
90%
63/70 runs under 3 min
RT coverage: 69 full · 1 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sat 3 Oct Max en route +31 min · last fix heading to Amsterdam Zuid +31 min
  • Sun 18 Oct Max en route +16 min · last fix heading to Schiphol Airport +16 min
  • Tue 25 Aug Max en route +13 min · last fix heading to Amsterdam Zuid +13 min
  • Thu 3 Sept Max en route +10 min · last fix heading to Amsterdam Zuid +10 min
  • Thu 17 Sept Max en route +9 min · last fix heading to Amsterdam Zuid +9 min

Distribution · 90 days

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

  • Early 24% · 17
  • On time 66% · 46
  • 3–10 min 4% · 3
  • 10–30 min 4% · 3
  • 30+ min 1% · 1

On-time by weekday

  • 100% M n=11
  • 92% T n=12
  • 100% W n=7
  • 75% T n=8
  • 100% F n=13
  • 82% S n=11
  • 75% S n=8

Stops and timetable

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

StopSched.
09:54
10:20 / 10:22
10:27 / 10:29
10:34
10:49 / 10:51
10:55
11:06

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.

Recent runs

DateLast stopFinalMax
Tue 27 OctAlmere Buiten 11:36No data—
Mon 26 OctAlmere Buiten 11:09No data—
Sun 25 OctDuivendrecht 10:51No data—
Sat 24 OctAlmere Buiten 11:09Partial coverage0 min+28 min
Fri 23 OctAlmere Buiten 12:160 min—
Thu 22 OctAlmere Buiten 11:30No data—
Wed 21 OctRotterdam Centraal 11:07No data—
Tue 20 OctAlmere Buiten 11:090 min—
Mon 19 OctAlmere Buiten 11:110 min—
Sun 18 OctSchiphol Airport 11:04+16 min+16 min
Sat 17 OctRotterdam Centraal 10:36No data—
Fri 16 OctAlmere Buiten 11:090 min—
Thu 15 OctAlmere Buiten 11:09No data—
Wed 14 OctAlmere Buiten 11:09No data—
Tue 13 OctAlmere Buiten 11:090 min—
Mon 12 OctAlmere Buiten 11:210 min—
Sun 11 OctDuivendrecht 10:49+1 min—
Sat 10 OctAlmere Buiten 11:090 min—
Fri 9 OctAlmere Buiten 11:090 min—
Thu 8 OctAlmere Buiten 11:090 min—
Wed 7 OctDuivendrecht 12:020 min—
Tue 6 OctAlmere Buiten 11:090 min—
Mon 5 OctAlmere Buiten 11:09−1 min—
Sun 4 OctAmsterdam Zuid 10:41No data—
Sat 3 OctAmsterdam Zuid 15:41+31 min+31 min
Fri 2 OctDuivendrecht 00:200 min+9 min
Thu 1 OctAlmere Buiten 11:09No data—
Wed 30 SeptAmsterdam Zuid 16:55+2 min+10 min
Tue 29 SeptDuivendrecht 00:44−1 min+11 min
Mon 28 SeptAmsterdam Zuid 19:000 min—