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: Friday 6 November 0 min

Next service: today 17:22 from Lelystad Centrum · Sat 7 Nov

Next departure 17:22 today · Lelystad Centrum
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 7 full · 12 partial · 10 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 7 full · 16 partial · 64 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: +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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=3
  • 67% S n=3

Stops and timetable

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

Last 90 days, 23 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 ≈ +1 min
18:12≈ on time ≈ +1 min
18:21≈ on time ≈ +1 min
18:29≈ on time ≈ +1 min
18:36≈ on time ≈ +1 min
18:43≈ on time ≈ +1 min
18:47≈ on time ≈ +2 min
18: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
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—
Mon 19 OctAkkrum 18:59Partial coverage0 min—
Sun 18 OctKampen Zuid 18:000 min—
Sat 17 OctKampen Zuid 17:59No data—
Fri 16 OctGrou-Jirnsum 19:01No data—
Thu 15 OctWolvega 19:00No data—
Wed 14 OctGrou-Jirnsum 19:01Partial coverage0 min—
Tue 13 OctHeerenveen 18:58Partial coverage0 min—
Mon 12 OctAkkrum 18:590 min—
Sun 11 OctKampen Zuid 17:580 min—
Sat 10 OctKampen Zuid 17:580 min—
Fri 9 OctHeerenveen 18:58Partial coverage0 min—
Thu 8 OctLelystad Centrum 18:59Partial coverage0 min—