Train NS 2442 Lelystad Centrum – Rotterdam Centraal

Lelystad Centrum 12:53 → Rotterdam Centraal 14:08 Daily 1 h 15 min · 7 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 14:43 No data

  1. Lelystad Centrum12:53
  2. Almere Buiten13:04
  3. Almere Centrum13:09
  4. Duivendrecht13:28
  5. Amsterdam Zuid13:33
  6. Schiphol Airport13:40
  7. Rotterdam Centraal14:08

Next service: tomorrow 12:53 from Lelystad Centrum · Fri 6 Nov

Next departure 12:53 tomorrow · Lelystad Centrum
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 10 full · 11 partial · 9 no data
On-time · 90 days
98%
60/61 runs under 3 min
RT coverage: 49 full · 12 partial · 25 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 Rotterdam Centraal, 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 10 Oct Max en route +35 min · last fix heading to Amsterdam Zuid +35 min

Distribution · 90 days

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

  • Early 30% · 18
  • On time 69% · 42
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=11
  • 100% T n=9
  • 100% W n=10
  • 100% T n=10
  • 100% F n=9
  • 86% S n=7
  • 100% S n=5

Stops and timetable

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

Last 90 days, 61 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
12:53on time on time
13:04≈ on time ≈ on time
13:09 / 13:11≈ on time ≈ on time
13:28≈ on time ≈ on time
13:33 / 13:34≈ on time ≈ on time
13:40 / 13:42≈ on time ≈ +1 min
14:08on 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
Thu 5 NovSchiphol Airport 14:43No data—
Wed 4 NovSchiphol Airport 14:09Partial coverage0 min—
Tue 3 NovSchiphol Airport 13:54No data—
Mon 2 NovSchiphol Airport 13:58Partial coverage0 min—
Sun 1 NovSchiphol Airport 14:100 min—
Sat 31 OctSchiphol Airport 14:090 min—
Fri 30 OctSchiphol Airport 14:09No data—
Thu 29 OctSchiphol Airport 14:09Partial coverage0 min—
Wed 28 OctSchiphol Airport 14:09No data—
Tue 27 OctLelystad Centrum 14:10No data—
Mon 26 OctSchiphol Airport 14:16Partial coverage0 min—
Sun 25 OctSchiphol Airport 14:10No data—
Sat 24 OctSchiphol Airport 14:090 min—
Fri 23 OctSchiphol Airport 14:44No data—
Thu 22 OctSchiphol Airport 14:10Partial coverage0 min—
Wed 21 OctLelystad Centrum 14:09No data—
Tue 20 OctSchiphol Airport 14:09Partial coverage0 min—
Mon 19 OctSchiphol Airport 14:09Partial coverage0 min—
Sun 18 OctSchiphol Airport 14:13+2 min+3 min
Sat 17 OctSchiphol Airport 14:100 min—
Fri 16 OctSchiphol Airport 14:100 min—
Thu 15 OctSchiphol Airport 14:10No data—
Wed 14 OctSchiphol Airport 14:14Partial coverage0 min—
Tue 13 OctSchiphol Airport 14:09Partial coverage0 min—
Mon 12 OctSchiphol Airport 14:100 min—
Sun 11 OctSchiphol Airport 14:160 min—
Sat 10 OctAmsterdam Zuid 14:49+35 min+35 min
Fri 9 OctSchiphol Airport 14:100 min—
Thu 8 OctSchiphol Airport 14:09Partial coverage0 min—
Wed 7 OctSchiphol Airport 14:42Partial coverage+1 min+1 min