Train NS 9068 Zwolle – Lelystad Centrum

Zwolle 19:07 → Lelystad Centrum 19:38 Daily 0 h 31 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 19:07 from Zwolle · Mon 16 Nov

Next departure 19:07 today · Zwolle
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 17 full · 4 partial · 8 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 23 full · 5 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Fri 13 Nov Max en route +5 min · last fix heading to Meppel +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 27
  • 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=5
  • 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 (4 stops).

Last 90 days, 28 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
19:07on time on time
19:17≈ on time ≈ on time
19:25≈ on time ≈ on time
19:38on 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
Sun 15 NovDronten 19:39Partial coverage0 min—
Sat 14 NovDronten 19:390 min—
Fri 13 NovMeppel 19:44+3 min+5 min
Thu 12 NovAkkrum 19:390 min—
Wed 11 NovGrou-Jirnsum 19:390 min—
Tue 10 NovAkkrum 19:390 min—
Mon 9 NovGrou-Jirnsum 19:040 min—
Sun 8 NovDronten 19:39Partial coverage0 min—
Sat 7 NovDronten 19:390 min—
Fri 6 NovMeppel 19:390 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:390 min—
Sun 1 NovDronten 19:39Partial coverage0 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:390 min—
Tue 27 OctLeeuwarden 19:400 min—
Mon 26 OctLeeuwarden 19:43No data—
Sun 25 OctDronten 19:39No data—
Sat 24 OctDronten 19:390 min—
Fri 23 OctDronten 19:40+1 min—
Thu 22 OctSteenwijk 19:40No data—
Wed 21 OctSteenwijk 19:40No data—
Tue 20 OctSteenwijk 19:390 min—
Mon 19 OctSteenwijk 19:400 min—
Sun 18 OctDronten 19:40Partial coverage0 min—
Sat 17 OctDronten 19:40No data—