Train NS 9024 Leeuwarden – Lelystad Centrum

Leeuwarden 07:03 → Lelystad Centrum 08:37 Mon, Tue, Wed, Thu, Fri, Sat 1 h 34 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 07:03 from Leeuwarden · Sat 7 Nov

Full trip card
Next departure 07:03 today · Leeuwarden
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 11 full · 10 partial · 4 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 11 full · 13 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
Leeuwarden
07:03on time on time
Grou-Jirnsum
07:12≈ on time ≈ on time
Akkrum
07:16≈ on time ≈ on time
Heerenveen
07:23≈ on time ≈ on time
Wolvega
07:30≈ on time ≈ on time
Steenwijk
07:38≈ on time ≈ on time
Meppel
07:47≈ on time ≈ on time
Zwolle
08:02 / 08:07≈ on time ≈ on time
Kampen Zuid
08:17≈ on time ≈ on time
Dronten
08:25≈ on time ≈ on time
Lelystad Centrum
08:37on time on time

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 6 NovDronten 08:39No data—
Thu 5 NovDronten 08:39No data—
Wed 4 NovDronten 08:39Partial coverage+1 min—
Tue 3 NovZwolle 09:080 min—
Mon 2 NovDronten 08:39No data—
Sat 31 OctDronten 08:39No data—
Fri 30 OctDronten 08:390 min—
Thu 29 OctDronten 08:39Partial coverage0 min—
Wed 28 OctDronten 08:40Partial coverage0 min—
Tue 27 OctDronten 08:390 min—
Mon 26 OctDronten 08:40Partial coverage0 min—
Sat 24 OctDronten 08:400 min—
Fri 23 OctDronten 08:39Partial coverage0 min—
Thu 22 OctDronten 08:39Partial coverage0 min—
Wed 21 OctDronten 08:410 min—
Tue 20 OctDronten 08:47Partial coverage0 min—
Mon 19 OctDronten 08:390 min—
Sat 17 OctDronten 08:400 min—
Fri 16 OctDronten 08:40Partial coverage0 min—
Thu 15 OctDronten 08:390 min—
Wed 14 OctDronten 08:390 min—
Tue 13 OctDronten 08:39Partial coverage0 min—
Mon 12 OctDronten 08:400 min—
Sat 10 OctDronten 08:390 min—
Fri 9 OctDronten 08:39Partial coverage0 min—
Thu 8 OctDronten 08:40Partial coverage0 min—
Wed 7 OctDronten 08:39Partial coverage0 min—
Tue 6 OctDronten 08:39Partial coverage0 min—
Mon 5 OctDronten 08:40No data—
Sat 3 OctDronten 08:40No data—