Train NS 9068 Leeuwarden – Lelystad Centrum

Leeuwarden 18:03 → Lelystad Centrum 19:38 Daily 1 h 35 min · 11 stops NS (Nederlandse Spoorwegen)

Running now · updated 18:45

Heading to Lelystad Centrum 0 min

Estimated arrival at Lelystad Centrum 19:38 · 7 km/h

  1. Leeuwarden18:03
  2. Akkrum18:16
  3. Heerenveen18:23
  4. Steenwijk18:38
  5. Zwolle19:02
  6. Kampen Zuid19:17
  7. Lelystad Centrum19:38

Today it is running worse than usual: typical arrival delay is 0 min; 91% of the last 22 runs arrived on time.

On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 9 full · 13 partial · 8 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 12 full · 18 partial · 53 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 Lelystad Centrum, 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 +5 min · last fix heading to Heerenveen +4 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Meppel +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 28
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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 10Today
18:03on time on time
18:12≈ on time ≈ on time
18:16≈ on time ≈ on time
18:23≈ on time ≈ on time
18:30≈ on time ≈ on time
18:38≈ on time ≈ on time
18:47≈ on time ≈ on time
19:02 / 19:07≈ on time ≈ on time
19:17≈ on time ≈ on time
19:25≈ on time ≈ on time
19:38on 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
Tue 17 NovHeerenveen 18:44Partial coverage0 min—
Mon 16 NovHeerenveen 19:49Partial coverage+4 min+5 min
Sun 15 NovDronten 19:390 min—
Sat 14 NovDronten 19:390 min—
Fri 13 NovMeppel 19:44Partial coverage+3 min+5 min
Thu 12 NovAkkrum 19:39Partial coverage0 min—
Wed 11 NovGrou-Jirnsum 19:39Partial coverage0 min—
Tue 10 NovAkkrum 19:39Partial coverage0 min—
Mon 9 NovGrou-Jirnsum 19:04Partial coverage0 min—
Sun 8 NovDronten 19:390 min—
Sat 7 NovDronten 19:390 min—
Fri 6 NovMeppel 19:39Partial coverage0 min—
Thu 5 NovGrou-Jirnsum 19:39No data—
Wed 4 NovGrou-Jirnsum 19:39No data—
Tue 3 NovGrou-Jirnsum 19:390 min—
Mon 2 NovLeeuwarden 19:39Partial coverage0 min—
Sun 1 NovDronten 19:390 min—
Sat 31 OctDronten 19:39No data—
Fri 30 OctMeppel 19:39No data—
Thu 29 Oct— 19:400 min+2 min
Wed 28 OctGrou-Jirnsum 19:39Partial coverage0 min—
Tue 27 OctLeeuwarden 19:40Partial coverage0 min—
Mon 26 OctLeeuwarden 19:43No data—
Sun 25 OctDronten 19:39No data—
Sat 24 OctDronten 19:390 min—
Fri 23 OctDronten 19:40Partial coverage+1 min—
Thu 22 OctSteenwijk 19:40No data—
Wed 21 OctSteenwijk 19:40No data—
Tue 20 OctSteenwijk 19:39Partial coverage0 min—
Mon 19 OctSteenwijk 19:400 min—