Train NS 9045 Lelystad Centrum – Zwolle

Lelystad Centrum 13:23 → Zwolle 13:54 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 13:23 from Lelystad Centrum · Mon 16 Nov

Next departure 13:23 today · Lelystad Centrum
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 18 full · 2 partial · 9 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 26 full · 3 partial · 58 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

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=5
  • 100% W n=4
  • 100% T n=2
  • 100% F n=4
  • 100% S n=5
  • 100% S n=5

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
13:23on time on time
13:35≈ on time ≈ on time
13:44≈ on time ≈ +1 min
13: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
Sun 15 NovKampen Zuid 13:58Partial coverage0 min—
Sat 14 NovKampen Zuid 13:580 min—
Fri 13 NovGrou-Jirnsum 15:030 min+1 min
Thu 12 NovGrou-Jirnsum 15:020 min—
Wed 11 NovGrou-Jirnsum 14:590 min—
Tue 10 NovGrou-Jirnsum 15:140 min—
Mon 9 NovGrou-Jirnsum 15:030 min—
Sun 8 NovKampen Zuid 13:580 min—
Sat 7 NovKampen Zuid 13:590 min—
Fri 6 NovGrou-Jirnsum 14:59No data—
Thu 5 NovGrou-Jirnsum 15:02No data—
Wed 4 NovGrou-Jirnsum 14:590 min—
Tue 3 NovGrou-Jirnsum 15:02No data—
Mon 2 NovGrou-Jirnsum 15:020 min—
Sun 1 NovKampen Zuid 14:00Partial coverage0 min—
Sat 31 OctKampen Zuid 13:580 min—
Fri 30 OctGrou-Jirnsum 15:020 min—
Thu 29 OctGrou-Jirnsum 15:02No data—
Wed 28 OctGrou-Jirnsum 15:01No data—
Tue 27 OctGrou-Jirnsum 15:020 min—
Mon 26 OctGrou-Jirnsum 15:01No data—
Sun 25 OctKampen Zuid 13:58No data—
Sat 24 OctKampen Zuid 13:580 min—
Fri 23 OctGrou-Jirnsum 15:080 min—
Thu 22 OctGrou-Jirnsum 15:03No data—
Wed 21 OctGrou-Jirnsum 15:02No data—
Tue 20 OctGrou-Jirnsum 15:020 min—
Mon 19 OctGrou-Jirnsum 15:010 min—
Sun 18 OctKampen Zuid 13:590 min—
Sat 17 OctKampen Zuid 13:59No data—