Train NS 4315 Hoofddorp – Lelystad Centrum

Hoofddorp 05:21 → Lelystad Centrum 06:33 Mon, Tue, Wed, Thu, Fri 1 h 12 min · 14 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

Next service: today 05:21 from Hoofddorp · Thu 5 Nov

Next departure 05:21 today · Hoofddorp
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 15 full · 6 partial · 0 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 18 full · 7 partial · 37 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: +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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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
05:21on time on time
05:25 / 05:31≈ on time ≈ on time
05:36 / 05:37≈ on time ≈ on time
05:40≈ on time ≈ on time
05:43 / 05:44≈ on time ≈ on time
05:46≈ on time ≈ on time
05:53 / 05:59≈ on time ≈ +1 min
06:05≈ on time ≈ +1 min
06:09≈ on time ≈ +1 min
06:12 / 06:13≈ on time ≈ +1 min
06:16≈ on time ≈ +1 min
06:19≈ on time ≈ +1 min
06:22≈ on time ≈ +1 min
06:33on 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
Wed 4 NovAlmere Oostvaarders 06:39Partial coverage+2 min+2 min
Tue 3 NovAlmere Oostvaarders 06:370 min—
Mon 2 NovAlmere Oostvaarders 06:34Partial coverage0 min—
Fri 30 OctAlmere Oostvaarders 06:370 min—
Thu 29 OctAlmere Oostvaarders 06:390 min—
Wed 28 OctAlmere Oostvaarders 06:390 min—
Tue 27 OctAlmere Oostvaarders 06:390 min—
Mon 26 OctAlmere Oostvaarders 06:40+1 min—
Fri 23 OctAlmere Oostvaarders 06:360 min—
Thu 22 OctAlmere Oostvaarders 06:39+2 min+3 min
Wed 21 OctAlmere Oostvaarders 06:38Partial coverage+1 min+1 min
Tue 20 OctAlmere Oostvaarders 06:37Partial coverage0 min—
Mon 19 OctAlmere Oostvaarders 06:37Partial coverage0 min—
Fri 16 OctAlmere Oostvaarders 06:400 min—
Thu 15 OctAlmere Oostvaarders 06:400 min—
Wed 14 OctAlmere Oostvaarders 06:40+1 min—
Tue 13 OctAlmere Oostvaarders 06:390 min—
Mon 12 OctAlmere Oostvaarders 06:41+2 min+2 min
Fri 9 OctAlmere Oostvaarders 06:370 min—
Thu 8 OctAlmere Oostvaarders 06:370 min—
Wed 7 OctAlmere Oostvaarders 06:38Partial coverage0 min+3 min
Tue 6 OctAlmere Oostvaarders 06:36Partial coverage0 min—
Mon 5 OctAmsterdam RAI 12:090 min—
Fri 2 OctAmsterdam RAI 18:390 min+4 min
Thu 1 OctAmsterdam RAI 18:590 min+2 min
Wed 30 SeptAlmere Oostvaarders 06:36No data—
Tue 29 SeptAlmere Oostvaarders 06:38No data—
Mon 28 SeptAlmere Oostvaarders 06:36No data—
Fri 25 SeptAlmere Oostvaarders 06:37No data—
Thu 24 SeptAlmere Oostvaarders 06:37No data—