Train NS 9016 Zwolle – Lelystad Centrum

Zwolle 06:07 → Lelystad Centrum 06:37 Mon, Tue, Wed, Thu, Fri 0 h 30 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Dronten at 06:39 0 min

  1. Zwolle06:07
  2. Kampen Zuid06:17
  3. Dronten06:25
  4. Lelystad Centrum06:37

Next service: tomorrow 06:07 from Zwolle · Thu 19 Nov

Next departure 06:07 tomorrow · Zwolle
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 13 full · 7 partial · 2 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 19 full · 10 partial · 33 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 29
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
06:07on time on time
06:17≈ on time ≈ on time
06:25≈ on time ≈ on time
06:37on 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 NovDronten 06:39Partial coverage0 min—
Tue 17 NovDronten 06:390 min—
Mon 16 NovDronten 06:39Partial coverage+1 min+1 min
Fri 13 NovDronten 06:490 min+2 min
Thu 12 NovDronten 06:390 min—
Wed 11 NovDronten 06:39Partial coverage0 min—
Tue 10 NovDronten 06:390 min—
Mon 9 NovDronten 06:42Partial coverage+2 min+2 min
Fri 6 NovDronten 06:39No data—
Thu 5 NovDronten 06:390 min—
Wed 4 NovDronten 06:39Partial coverage+1 min—
Tue 3 NovDronten 06:390 min—
Mon 2 NovDronten 06:39No data—
Fri 30 OctDronten 06:400 min—
Thu 29 OctDronten 06:400 min—
Wed 28 OctDronten 06:500 min—
Tue 27 OctDronten 06:390 min—
Mon 26 OctDronten 06:40Partial coverage0 min—
Fri 23 OctDronten 06:390 min—
Thu 22 OctDronten 06:400 min—
Wed 21 OctDronten 06:42Partial coverage+2 min+3 min
Tue 20 OctDronten 06:400 min—
Mon 19 OctDronten 06:39Partial coverage0 min+8 min
Fri 16 OctDronten 06:390 min—
Thu 15 OctDronten 06:400 min—
Wed 14 OctDronten 06:40Partial coverage0 min—
Tue 13 OctDronten 06:390 min—
Fri 9 OctDronten 06:400 min—
Thu 8 OctDronten 06:40+2 min+2 min
Wed 7 OctDronten 06:39Partial coverage0 min—