Train NS Int 9715 Rotterdam Centraal – Lelystad Centrum

Rotterdam Centraal 06:22 → Lelystad Centrum 07:36 Mon, Tue, Wed, Thu, Fri 1 h 14 min · 7 stops NS Int

✓ Today’s run finished

Today, last fix heading to Almere Buiten at 07:39 +3 min

  1. Rotterdam Centraal06:22
  2. Schiphol Airport06:48
  3. Amsterdam Zuid06:55
  4. Duivendrecht07:00
  5. Almere Centrum07:17
  6. Almere Buiten07:25
  7. Lelystad Centrum07:36

Next service: Monday 06:22 from Rotterdam Centraal · Mon 23 Nov

Next departure 06:22 Monday · Rotterdam Centraal
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 17 full · 4 partial · 1 no data
On-time · 90 days
95%
57/60 runs under 3 min
RT coverage: 54 full · 6 partial · 5 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: +2 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

  • Wed 14 Oct Max en route +26 min · last fix heading to Almere Buiten +20 min
  • Thu 8 Oct Max en route +7 min · last fix heading to Almere Buiten +5 min
  • Wed 21 Oct Max en route +3 min · last fix heading to Almere Buiten +3 min

Distribution · 90 days

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

  • Early 15% · 9
  • On time 80% · 48
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=13
  • 82% W n=11
  • 92% T n=12
  • 100% F n=11
  • 100% S n=2
  • — S n=0

Stops and timetable

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

Last 90 days, 60 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
06:22on time on time
06:48 / 06:49≈ on time ≈ +1 min
06:55 / 06:56≈ on time ≈ +1 min
07:00 / 07:01≈ on time ≈ +1 min
07:17 / 07:20≈ on time ≈ +2 min
07:25≈ on time ≈ +2 min
07:36on 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 07:39Partial coverage+3 min+4 min
Thu 19 NovAlmere Buiten 07:42+2 min+3 min
Wed 18 NovAlmere Buiten 07:390 min—
Tue 17 NovAlmere Buiten 07:390 min—
Mon 16 NovAlmere Buiten 07:390 min—
Fri 13 NovAlmere Buiten 07:39Partial coverage0 min—
Thu 12 NovAlmere Buiten 07:39+2 min+2 min
Wed 11 NovAlmere Buiten 07:390 min—
Tue 10 NovSchiphol Airport 07:03+1 min+1 min
Mon 9 NovAlmere Buiten 07:390 min—
Fri 6 NovAlmere Buiten 07:39No data—
Thu 5 NovAlmere Buiten 08:090 min—
Wed 4 NovAlmere Buiten 07:390 min—
Tue 3 NovAlmere Buiten 07:39+2 min+3 min
Mon 2 NovAlmere Buiten 07:390 min—
Fri 30 OctAlmere Buiten 07:39Partial coverage0 min—
Thu 29 OctAlmere Buiten 07:400 min—
Wed 28 OctAlmere Buiten 07:390 min—
Tue 27 OctAlmere Buiten 07:390 min—
Mon 26 OctAlmere Buiten 07:390 min—
Fri 23 OctAlmere Buiten 07:40Partial coverage+2 min+2 min
Thu 22 OctAlmere Buiten 07:390 min—
Wed 21 OctAlmere Buiten 07:40+3 min+3 min
Tue 20 OctAlmere Buiten 07:390 min—
Mon 19 OctAlmere Buiten 07:41+2 min+2 min
Fri 16 OctAlmere Buiten 07:39Partial coverage0 min—
Thu 15 OctAlmere Buiten 07:40+1 min—
Wed 14 OctAlmere Buiten 08:17+20 min+26 min
Tue 13 OctAlmere Buiten 07:390 min—
Fri 9 OctAlmere Buiten 07:39Partial coverage0 min—