Train NS 9021 Lelystad Centrum – Leeuwarden

Lelystad Centrum 07:22 → Leeuwarden 08:57 Mon, Tue, Wed, Thu, Fri, Sun 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Kampen Zuid at 08:59 0 min

  1. Lelystad Centrum07:22
  2. Kampen Zuid07:43
  3. Zwolle07:53
  4. Steenwijk08:21
  5. Heerenveen08:36
  6. Akkrum08:43
  7. Leeuwarden08:57

Next service: tomorrow 07:22 from Lelystad Centrum · Mon 9 Nov

Next departure 07:22 tomorrow · Lelystad Centrum
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 5 full · 11 partial · 9 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 6 full · 14 partial · 57 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 Leeuwarden, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 1 Nov Max en route +3 min · last fix heading to Kampen Zuid +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
07:22on time on time
07:35≈ on time ≈ on time
07:43≈ on time ≈ on time
07:53 / 07:57≈ on time ≈ +1 min
08:12≈ on time ≈ +1 min
08:21≈ on time ≈ +1 min
08:29≈ on time ≈ +1 min
08:36≈ on time ≈ +1 min
08:43≈ on time ≈ +2 min
08:47≈ on time ≈ +2 min
08:57on 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
Sun 8 NovKampen Zuid 08:590 min—
Fri 6 NovGrou-Jirnsum 09:02No data—
Thu 5 NovGrou-Jirnsum 09:02No data—
Wed 4 NovGrou-Jirnsum 09:04Partial coverage+2 min+4 min
Tue 3 NovGrou-Jirnsum 09:04No data—
Mon 2 NovGrou-Jirnsum 09:04Partial coverage0 min—
Sun 1 NovKampen Zuid 07:58+3 min+3 min
Fri 30 OctGrou-Jirnsum 09:01Partial coverage0 min—
Thu 29 OctGrou-Jirnsum 09:01Partial coverage0 min—
Wed 28 OctGrou-Jirnsum 09:060 min—
Tue 27 OctGrou-Jirnsum 09:03Partial coverage0 min—
Mon 26 OctGrou-Jirnsum 09:02Partial coverage0 min—
Sun 25 OctKampen Zuid 08:59No data—
Fri 23 OctGrou-Jirnsum 09:02Partial coverage0 min—
Thu 22 OctGrou-Jirnsum 09:03Partial coverage0 min—
Wed 21 OctGrou-Jirnsum 09:02No data—
Tue 20 OctGrou-Jirnsum 09:03Partial coverage0 min—
Mon 19 OctGrou-Jirnsum 09:02Partial coverage0 min—
Sun 18 OctKampen Zuid 07:560 min—
Fri 16 OctGrou-Jirnsum 09:01Partial coverage0 min—
Thu 15 OctGrou-Jirnsum 09:02No data—
Wed 14 OctGrou-Jirnsum 09:04No data—
Tue 13 OctGrou-Jirnsum 09:01No data—
Mon 12 OctGrou-Jirnsum 09:04No data—
Sun 11 OctKampen Zuid 08:590 min—
Fri 9 OctGrou-Jirnsum 09:02Partial coverage0 min—
Thu 8 OctGrou-Jirnsum 09:03Partial coverage+1 min+1 min
Wed 7 OctGrou-Jirnsum 09:010 min—
Tue 6 OctGrou-Jirnsum 09:02Partial coverage0 min—
Mon 5 OctGrou-Jirnsum 09:02No data—