Train NS 9015 Lelystad Centrum – Leeuwarden

Lelystad Centrum 05:52 → Leeuwarden 07:27 Mon, Tue, Wed, Thu, Fri, Sat 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Grou-Jirnsum at 07:33 +1 min

  1. Lelystad Centrum05:52
  2. Kampen Zuid06:13
  3. Zwolle06:23
  4. Steenwijk06:51
  5. Heerenveen07:06
  6. Grou-Jirnsum07:17
  7. Leeuwarden07:27

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

Next departure 05:52 tomorrow · Lelystad Centrum
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 10 full · 11 partial · 3 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 16 full · 15 partial · 43 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

  • Sat 31 Oct Max en route +6 min · last fix heading to Grou-Jirnsum +5 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 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
05:52on time on time
06:05≈ on time ≈ on time
06:13≈ on time ≈ on time
06:23 / 06:27≈ on time ≈ +1 min
06:42≈ on time ≈ +1 min
06:51≈ on time ≈ +1 min
06:59≈ on time ≈ +1 min
07:06≈ on time ≈ +1 min
07:13≈ on time ≈ +1 min
07:17≈ on time ≈ +2 min
07:27on 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
Mon 16 NovGrou-Jirnsum 07:33Partial coverage+1 min+2 min
Sat 14 NovGrou-Jirnsum 07:330 min+2 min
Fri 13 NovGrou-Jirnsum 07:330 min+2 min
Thu 12 NovZwolle 07:49Partial coverage0 min+11 min
Wed 11 NovGrou-Jirnsum 07:29Partial coverage0 min—
Tue 10 NovGrou-Jirnsum 07:32Partial coverage0 min—
Mon 9 NovGrou-Jirnsum 07:320 min—
Sat 7 NovGrou-Jirnsum 07:320 min—
Fri 6 NovGrou-Jirnsum 07:34No data—
Thu 5 NovGrou-Jirnsum 07:34Partial coverage0 min—
Wed 4 NovGrou-Jirnsum 07:33Partial coverage+1 min+2 min
Tue 3 NovGrou-Jirnsum 07:320 min—
Mon 2 NovGrou-Jirnsum 07:32No data—
Sat 31 OctGrou-Jirnsum 07:37+5 min+6 min
Fri 30 OctGrou-Jirnsum 07:32+2 min+2 min
Thu 29 OctGrou-Jirnsum 07:32Partial coverage0 min—
Wed 28 OctGrou-Jirnsum 07:33Partial coverage+1 min—
Tue 27 OctGrou-Jirnsum 07:31Partial coverage0 min—
Mon 26 OctGrou-Jirnsum 07:32+1 min—
Fri 23 OctGrou-Jirnsum 07:310 min—
Thu 22 OctGrou-Jirnsum 07:32Partial coverage0 min—
Wed 21 OctGrou-Jirnsum 07:31Partial coverage0 min—
Tue 20 OctGrou-Jirnsum 07:33+1 min+1 min
Mon 19 OctGrou-Jirnsum 07:31No data—
Sat 17 OctGrou-Jirnsum 07:31No data—
Fri 16 OctGrou-Jirnsum 07:310 min—
Thu 15 OctGrou-Jirnsum 07:32Partial coverage0 min—
Wed 14 OctGrou-Jirnsum 07:32Partial coverage0 min—
Tue 13 OctGrou-Jirnsum 07:320 min—
Mon 12 OctGrou-Jirnsum 07:310 min—