Train NS 9061 Lelystad Centrum – Leeuwarden

Lelystad Centrum 17:22 → Leeuwarden 18:57 Daily 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 17:22 from Lelystad Centrum · Thu 19 Nov

Next departure 17:22 today · Lelystad Centrum
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 7 full · 15 partial · 7 no data
On-time · 90 days
91%
32/35 runs under 3 min
RT coverage: 11 full · 24 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Mon 16 Nov Max en route +7 min · last fix heading to Steenwijk +6 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Grou-Jirnsum +5 min
  • Sun 1 Nov Max en route +8 min · last fix heading to Kampen Zuid +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 32
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 75% F n=4
  • 100% S n=5
  • 80% S n=5

Stops and timetable

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

Last 90 days, 35 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
17:22on time on time
17:34≈ on time ≈ on time
17:43≈ on time ≈ on time
17:53 / 17:57≈ on time ≈ on time
18:12≈ on time ≈ on time
18:21≈ on time ≈ on time
18:29≈ on time ≈ on time
18:36≈ on time ≈ on time
18:43≈ on time ≈ on time
18:47≈ on time ≈ on time
18:57on 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
Wed 18 NovAkkrum 18:58Partial coverage0 min—
Tue 17 NovSteenwijk 18:59Partial coverage+2 min+3 min
Mon 16 NovSteenwijk 19:09Partial coverage+6 min+7 min
Sun 15 NovKampen Zuid 17:590 min—
Sat 14 NovKampen Zuid 17:590 min—
Fri 13 NovGrou-Jirnsum 18:59Partial coverage+5 min+5 min
Thu 12 NovSteenwijk 18:59Partial coverage+1 min—
Wed 11 NovMeppel 18:59Partial coverage+1 min+1 min
Tue 10 NovSteenwijk 18:59Partial coverage+1 min+1 min
Mon 9 NovMeppel 18:24Partial coverage0 min—
Sun 8 NovKampen Zuid 17:580 min—
Sat 7 NovKampen Zuid 17:580 min—
Fri 6 NovGrou-Jirnsum 18:59Partial coverage0 min—
Thu 5 NovMeppel 18:59Partial coverage0 min—
Wed 4 NovMeppel 18:59No data—
Tue 3 NovMeppel 18:58No data—
Mon 2 NovDronten 18:59Partial coverage+2 min+2 min
Sun 1 NovKampen Zuid 18:04+4 min+8 min
Sat 31 OctKampen Zuid 17:590 min—
Fri 30 OctGrou-Jirnsum 19:01No data—
Thu 29 OctKampen Zuid 18:45Partial coverage0 min—
Wed 28 OctMeppel 18:58Partial coverage0 min—
Tue 27 OctDronten 19:01No data—
Mon 26 OctDronten 18:59Partial coverage0 min—
Sun 25 OctKampen Zuid 17:59No data—
Sat 24 OctKampen Zuid 17:580 min—
Fri 23 OctGrou-Jirnsum 19:02Partial coverage+2 min+2 min
Thu 22 OctAkkrum 19:01No data—
Wed 21 OctHeerenveen 18:59No data—
Tue 20 OctAkkrum 18:50Partial coverage0 min—