Train NS 9073 Lelystad Centrum – Zwolle

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 20:23 from Lelystad Centrum · Sun 8 Nov

Next departure 20:23 today · Lelystad Centrum
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 13 full · 4 partial · 11 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 18 full · 4 partial · 31 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

Worst days

  • Mon 5 Oct Max en route +8 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
20:23on time on time
20:35≈ on time ≈ on time
20:44≈ on time ≈ on time
20: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
Sat 7 NovKampen Zuid 20:58Partial coverage0 min—
Fri 6 Nov— 20:540 min—
Thu 5 Nov— 20:550 min—
Wed 4 Nov— 20:540 min—
Tue 3 Nov— 20:540 min—
Sun 1 NovKampen Zuid 20:58No data—
Sat 31 OctKampen Zuid 20:580 min—
Fri 30 Oct— 21:17No data—
Thu 29 Oct— 20:540 min—
Wed 28 Oct— 20:540 min—
Tue 27 Oct— 20:55No data—
Mon 26 Oct— 21:06No data—
Sun 25 OctKampen Zuid 20:58No data—
Sat 24 OctKampen Zuid 21:04Partial coverage0 min—
Fri 23 Oct— 20:550 min—
Thu 22 Oct— 20:55No data—
Wed 21 Oct— 21:03No data—
Tue 20 Oct— 20:540 min—
Mon 19 Oct— 20:570 min—
Sun 18 OctKampen Zuid 20:58Partial coverage0 min—
Sat 17 OctKampen Zuid 20:58No data—
Fri 16 Oct— 20:540 min—
Thu 15 Oct— 20:54No data—
Wed 14 Oct— 21:590 min—
Tue 13 Oct— 20:55No data—
Mon 12 Oct— 20:54No data—
Sun 11 OctKampen Zuid 20:580 min—
Sat 10 OctKampen Zuid 20:58Partial coverage0 min—
Fri 9 Oct— 20:540 min—
Thu 8 Oct— 20:55+1 min+1 min