Train NS 9048 Zwolle – Lelystad Centrum

Zwolle 14:07 → Lelystad Centrum 14:38 Daily 0 h 31 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Dronten at 14:39 0 min

  1. Zwolle14:07
  2. Kampen Zuid14:17
  3. Dronten14:25
  4. Lelystad Centrum14:38

Next service: tomorrow 14:07 from Zwolle · Sun 8 Nov

Next departure 14:07 tomorrow · Zwolle
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 16 full · 5 partial · 9 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 20 full · 5 partial · 61 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 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

  • Wed 4 Nov Max en route +9 min · last fix heading to Dronten +9 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Dronten +4 min

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 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 50% T n=2
  • 80% W n=5
  • 100% T n=5
  • 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, 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
14:07on time on time
14:17≈ on time ≈ +1 min
14:25≈ on time ≈ +1 min
14:38on time +2 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 NovDronten 14:39Partial coverage0 min—
Fri 6 NovDronten 14:39No data—
Thu 5 NovDronten 14:490 min—
Wed 4 NovDronten 14:49+9 min+9 min
Tue 3 NovDronten 14:39No data—
Mon 2 NovDronten 14:39No data—
Sun 1 NovDronten 14:410 min—
Sat 31 OctDronten 14:40Partial coverage0 min—
Fri 30 OctDronten 14:420 min—
Thu 29 OctDronten 14:420 min—
Wed 28 OctDronten 14:410 min—
Tue 27 OctDronten 14:44No data—
Mon 26 OctDronten 14:41No data—
Sun 25 OctDronten 14:39No data—
Sat 24 OctDronten 14:40Partial coverage0 min—
Fri 23 OctDronten 14:420 min—
Thu 22 OctDronten 14:390 min—
Wed 21 OctDronten 14:400 min—
Tue 20 OctDronten 14:400 min—
Mon 19 OctDronten 14:410 min—
Sun 18 OctDronten 14:39Partial coverage0 min—
Sat 17 OctDronten 14:39No data—
Fri 16 OctDronten 14:400 min—
Thu 15 OctDronten 14:390 min—
Wed 14 OctDronten 14:390 min—
Tue 13 OctDronten 14:42No data—
Mon 12 OctDronten 14:40No data—
Sun 11 OctDronten 14:400 min—
Sat 10 OctDronten 14:40Partial coverage0 min—
Fri 9 OctDronten 14:400 min—