Train NS 9069 Lelystad Centrum – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Kampen Zuid at 19:58 0 min

  1. Lelystad Centrum19:23
  2. Dronten19:35
  3. Kampen Zuid19:44
  4. Zwolle19:54

Next service: tomorrow 19:23 from Lelystad Centrum · Sun 15 Nov

Next departure 19:23 tomorrow · Lelystad Centrum
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 14 full · 8 partial · 8 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 21 full · 10 partial · 27 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 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

  • Thu 29 Oct Max en route +19 min · last fix heading to — +18 min
  • Thu 8 Oct Max en route +9 min · last fix heading to — +9 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=3
  • 50% T n=4
  • 100% F n=6
  • 100% S n=6
  • 100% 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
19:23on time on time
19:35≈ on time ≈ +1 min
19:44≈ on time ≈ +2 min
19:54on time +3 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 14 NovKampen Zuid 19:58Partial coverage0 min—
Fri 13 Nov— 20:580 min—
Thu 12 Nov— 20:59+1 min+1 min
Wed 11 Nov— 20:580 min—
Tue 10 Nov— 20:580 min—
Mon 9 Nov— 19:440 min—
Sun 8 NovKampen Zuid 19:58Partial coverage0 min—
Sat 7 NovKampen Zuid 19:58Partial coverage0 min—
Fri 6 Nov— 20:59+1 min+3 min
Thu 5 Nov— 20:59No data—
Wed 4 Nov— 20:59+1 min—
Tue 3 Nov— 20:58No data—
Mon 2 Nov— 20:59No data—
Sun 1 NovKampen Zuid 19:59Partial coverage0 min—
Sat 31 OctKampen Zuid 19:59Partial coverage0 min—
Fri 30 Oct— 20:590 min—
Thu 29 Oct— 21:34+18 min+19 min
Wed 28 Oct— 20:58No data—
Tue 27 Oct— 21:000 min—
Mon 26 OctKampen Zuid 21:04No data—
Sun 25 OctKampen Zuid 19:58No data—
Sat 24 OctKampen Zuid 20:04Partial coverage0 min—
Fri 23 OctLelystad Centrum 21:03+3 min+3 min
Thu 22 Oct— 21:000 min—
Wed 21 Oct— 21:03No data—
Tue 20 Oct— 20:590 min—
Mon 19 Oct— 21:01No data—
Sun 18 OctKampen Zuid 19:58Partial coverage0 min—
Sat 17 OctKampen Zuid 19:58Partial coverage0 min—
Fri 16 OctDronten 20:580 min—