Train NS 9032 Zwolle – Lelystad Centrum

Zwolle 10:07 → Lelystad Centrum 10:37 Daily 0 h 30 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November +5 min

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

Next departure 10:07 today · Zwolle
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 20 full · 1 partial · 8 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 29 full · 2 partial · 54 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: 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

  • Sun 11 Oct Max en route +14 min · last fix heading to Dronten +14 min
  • Sun 15 Nov Max en route +5 min · last fix heading to Dronten +5 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=4
  • 100% T n=6
  • 100% F n=3
  • 100% S n=6
  • 50% S n=4

Stops and timetable

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

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