Train NS 9064 Zwolle – Lelystad Centrum

Zwolle 18:07 → Lelystad Centrum 18: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 18:07 from Zwolle · Mon 16 Nov

Next departure 18:07 today · Zwolle
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 16 full · 7 partial · 6 no data
On-time · 90 days
97%
31/32 runs under 3 min
RT coverage: 23 full · 9 partial · 53 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

  • Wed 7 Oct Max en route +13 min · last fix heading to Zwolle +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 31
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 75% W n=4
  • 100% T n=4
  • 100% 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, 32 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
18:07on time on time
18:17≈ on time ≈ on time
18:25≈ on time ≈ on time
18: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
Sun 15 NovDronten 18:39Partial coverage0 min—
Sat 14 NovDronten 18:39Partial coverage0 min—
Fri 13 NovDronten 18:390 min—
Thu 12 NovKampen Zuid 18:390 min—
Wed 11 NovZwolle 18:390 min+3 min
Tue 10 NovKampen Zuid 18:390 min—
Mon 9 NovMeppel 18:040 min—
Sun 8 NovDronten 18:39Partial coverage0 min—
Sat 7 NovDronten 18:39Partial coverage0 min—
Fri 6 NovDronten 18:400 min—
Thu 5 NovZwolle 18:390 min—
Wed 4 NovZwolle 18:390 min—
Tue 3 NovZwolle 18:39No data—
Mon 2 NovZwolle 18:390 min—
Sun 1 NovDronten 18:39Partial coverage0 min—
Sat 31 OctDronten 18:40No data—
Fri 30 OctDronten 18:43No data—
Thu 29 OctMeppel 18:39No data—
Wed 28 OctZwolle 18:390 min—
Tue 27 OctMeppel 18:400 min—
Mon 26 OctZwolle 18:390 min—
Sun 25 OctDronten 18:40No data—
Sat 24 OctDronten 18:40Partial coverage0 min—
Fri 23 OctDronten 18:39+1 min—
Thu 22 OctDronten 18:390 min—
Wed 21 OctDronten 18:40No data—
Tue 20 OctDronten 18:400 min—
Mon 19 OctDronten 18:420 min—
Sun 18 OctZwolle 18:40Partial coverage0 min—
Sat 17 OctDronten 18:40No data—