Train NS 9089 Lelystad Centrum – Zwolle

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

✓ Today’s run finished

Today, last fix heading to — at 00:54 0 min

  1. Lelystad Centrum00:23
  2. Dronten00:36
  3. Kampen Zuid00:44
  4. Zwolle00:54

Next service: tomorrow 00:23 from Lelystad Centrum · Fri 6 Nov

Next departure 00:23 tomorrow · Lelystad Centrum
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 2 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 10 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 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

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

  • Early 0% · 0
  • On time 100% · 25
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 100% S n=3
  • 100% S n=1

Stops and timetable

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

Last 90 days, 25 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
00:23on time on time
00:36≈ on time ≈ on time
00:44≈ on time ≈ on time
00:54on 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
Thu 5 Nov— 00:540 min—
Wed 4 Nov— 00:540 min—
Tue 3 Nov— 00:540 min—
Mon 2 NovKampen Zuid 00:580 min—
Fri 30 Oct— 00:550 min—
Thu 29 Oct— 00:550 min—
Wed 28 Oct— 00:560 min—
Tue 27 Oct— 00:550 min—
Mon 26 OctKampen Zuid 00:58No data—
Sat 24 Oct— 00:570 min—
Fri 23 Oct— 00:550 min—
Thu 22 Oct— 00:550 min—
Wed 21 Oct— 01:080 min—
Tue 20 Oct— 00:560 min—
Mon 19 OctKampen Zuid 00:590 min—
Sun 18 OctKampen Zuid 00:58No data—
Sat 17 Oct— 00:540 min—
Fri 16 Oct— 01:160 min—
Thu 15 Oct— 00:540 min—
Wed 14 Oct— 00:540 min—
Tue 13 Oct— 00:550 min—
Sun 11 Oct— 00:570 min—
Sat 10 Oct— 00:560 min—
Fri 9 Oct— 00:550 min—
Thu 8 Oct— 00:550 min—
Wed 7 Oct— 00:550 min—
Tue 6 Oct— 00:550 min—
Sun 4 OctDronten 00:50No data—
Mon 28 SeptKampen Zuid 00:57No data—
Mon 21 SeptKampen Zuid 00:58No data—