Train NS 9088 Zwolle – Lelystad Centrum

Zwolle 00:07 → Lelystad Centrum 00:38 Mon, Tue, Wed, Thu, Sun 0 h 31 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Zwolle00:07
  2. Kampen Zuid00:17
  3. Dronten00:25
  4. Lelystad Centrum00:38

Next service: Sunday 00:07 from Zwolle · Sun 22 Nov

Next departure 00:07 Sunday · Zwolle
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 2 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 9 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: +1 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 15 Nov Max en route +8 min · last fix heading to Dronten +7 min

Distribution · 90 days

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

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

On-time by weekday

  • — M n=0
  • 100% T n=7
  • 100% W n=6
  • 100% T n=7
  • 100% F n=6
  • — S n=0
  • 75% S n=4

Stops and timetable

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

Last 90 days, 30 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:07on time on time
00:17≈ on time ≈ on time
00:25≈ on time ≈ on time
00:38on 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
Fri 20 Nov— 00:390 min—
Thu 19 Nov— 00:440 min—
Wed 18 Nov— 00:440 min—
Tue 17 Nov— 00:390 min—
Sun 15 NovDronten 00:49+7 min+8 min
Fri 13 Nov— 00:390 min—
Thu 12 Nov— 00:390 min—
Wed 11 Nov— 00:390 min—
Tue 10 Nov— 00:390 min+3 min
Sun 8 NovDronten 00:43+2 min+4 min
Fri 6 Nov— 00:440 min—
Thu 5 Nov— 00:390 min—
Wed 4 Nov— 00:390 min—
Tue 3 Nov— 00:390 min—
Sun 1 NovDronten 00:390 min—
Fri 30 Oct— 00:390 min—
Thu 29 Oct— 00:390 min—
Wed 28 Oct— 00:370 min—
Tue 27 Oct— 00:390 min—
Sun 25 OctDronten 00:40No data—
Fri 23 Oct— 00:39No data—
Thu 22 Oct— 00:400 min—
Tue 20 Oct— 00:400 min—
Sun 18 OctDronten 00:400 min—
Fri 16 Oct— 00:400 min—
Thu 15 Oct— 00:420 min—
Wed 14 Oct— 00:390 min—
Tue 13 Oct— 00:390 min—
Fri 9 Oct— 00:390 min—
Thu 8 Oct— 00:390 min—