Train NS 9037 Lelystad Centrum – Zwolle

Lelystad Centrum 11:23 → Zwolle 11:54 Daily 0 h 31 min · 4 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 11:23 from Lelystad Centrum · Sun 8 Nov

Next departure 11:23 today · Lelystad Centrum
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 15 full · 4 partial · 10 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 20 full · 4 partial · 63 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 Zwolle, 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 5 Oct Max en route +4 min · last fix heading to Grou-Jirnsum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=4
  • 100% W n=3
  • 100% T n=3
  • 100% F n=4
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 24 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
11:23on time on time
11:36≈ on time ≈ on time
11:44≈ on time ≈ on time
11:54on 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
Sat 7 NovKampen Zuid 11:59Partial coverage0 min—
Fri 6 NovGrou-Jirnsum 13:04No data—
Thu 5 NovGrou-Jirnsum 12:59No data—
Wed 4 NovGrou-Jirnsum 13:02+1 min+1 min
Tue 3 NovGrou-Jirnsum 13:040 min—
Mon 2 NovGrou-Jirnsum 12:590 min—
Sun 1 NovKampen Zuid 11:590 min—
Sat 31 OctKampen Zuid 11:58Partial coverage0 min—
Fri 30 OctGrou-Jirnsum 13:030 min—
Thu 29 OctGrou-Jirnsum 13:08No data—
Wed 28 OctGrou-Jirnsum 13:04No data—
Tue 27 OctGrou-Jirnsum 13:03No data—
Mon 26 OctGrou-Jirnsum 13:16No data—
Sun 25 OctKampen Zuid 11:59No data—
Sat 24 OctKampen Zuid 11:59Partial coverage0 min—
Fri 23 OctGrou-Jirnsum 13:010 min—
Thu 22 OctGrou-Jirnsum 13:010 min—
Wed 21 OctGrou-Jirnsum 13:01No data—
Tue 20 OctGrou-Jirnsum 13:020 min—
Mon 19 OctGrou-Jirnsum 13:010 min—
Sun 18 OctKampen Zuid 12:000 min+1 min
Sat 17 OctKampen Zuid 11:59No data—
Fri 16 OctGrou-Jirnsum 13:020 min—
Thu 15 OctGrou-Jirnsum 13:010 min—
Wed 14 OctGrou-Jirnsum 13:030 min—
Tue 13 OctGrou-Jirnsum 13:010 min—
Mon 12 OctGrou-Jirnsum 13:02No data—
Sun 11 OctKampen Zuid 11:590 min—
Sat 10 OctKampen Zuid 12:00Partial coverage+1 min—
Fri 9 OctGrou-Jirnsum 13:050 min—