Train NS 9023 Lelystad Centrum – Leeuwarden

Lelystad Centrum 07:52 → Leeuwarden 09:27 Daily 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Grou-Jirnsum at 09:32 0 min

  1. Lelystad Centrum07:52
  2. Kampen Zuid08:13
  3. Zwolle08:23
  4. Steenwijk08:51
  5. Heerenveen09:06
  6. Grou-Jirnsum09:17
  7. Leeuwarden09:27

Next service: tomorrow 07:52 from Lelystad Centrum · Tue 17 Nov

Next departure 07:52 tomorrow · Lelystad Centrum
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 5 full · 18 partial · 7 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 5 full · 26 partial · 56 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 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

  • Wed 4 Nov Max en route +12 min · last fix heading to Grou-Jirnsum +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 30
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 75% W n=4
  • 100% T n=4
  • 100% F n=5
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 31 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:52on time on time
08:05≈ on time ≈ on time
08:13≈ on time ≈ on time
08:23 / 08:27≈ on time ≈ on time
08:42≈ on time ≈ on time
08:51≈ on time ≈ on time
08:59≈ on time ≈ on time
09:06≈ on time ≈ +1 min
09:13≈ on time ≈ +1 min
09:17≈ on time ≈ +1 min
09:27on 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
Mon 16 NovGrou-Jirnsum 09:32Partial coverage0 min—
Sun 15 NovGrou-Jirnsum 09:32+1 min—
Sat 14 NovGrou-Jirnsum 09:33Partial coverage+1 min+2 min
Fri 13 NovGrou-Jirnsum 09:34Partial coverage+2 min+3 min
Thu 12 NovGrou-Jirnsum 09:29Partial coverage0 min—
Wed 11 NovGrou-Jirnsum 09:32Partial coverage+1 min—
Tue 10 NovGrou-Jirnsum 09:34Partial coverage+3 min+4 min
Mon 9 NovGrou-Jirnsum 09:32Partial coverage0 min—
Sun 8 NovGrou-Jirnsum 09:32Partial coverage0 min—
Sat 7 NovGrou-Jirnsum 09:320 min—
Fri 6 NovGrou-Jirnsum 09:32No data—
Thu 5 NovGrou-Jirnsum 09:38No data—
Wed 4 NovGrou-Jirnsum 09:44Partial coverage+12 min+12 min
Tue 3 NovGrou-Jirnsum 09:32No data—
Mon 2 NovGrou-Jirnsum 09:43No data—
Sun 1 NovGrou-Jirnsum 09:320 min+2 min
Sat 31 OctGrou-Jirnsum 09:31Partial coverage0 min—
Fri 30 OctGrou-Jirnsum 09:32Partial coverage0 min—
Thu 29 OctGrou-Jirnsum 09:31Partial coverage0 min—
Wed 28 OctGrou-Jirnsum 09:320 min—
Tue 27 OctLelystad Centrum 09:42Partial coverage0 min—
Mon 26 OctGrou-Jirnsum 09:32Partial coverage0 min—
Sun 25 OctKampen Zuid 08:28No data—
Sat 24 OctKampen Zuid 08:280 min—
Fri 23 OctGrou-Jirnsum 09:31Partial coverage0 min—
Thu 22 OctGrou-Jirnsum 09:53Partial coverage0 min—
Wed 21 OctGrou-Jirnsum 09:31No data—
Tue 20 OctGrou-Jirnsum 09:32Partial coverage0 min—
Mon 19 OctGrou-Jirnsum 09:32No data—
Sun 18 OctGrou-Jirnsum 09:32Partial coverage+1 min—