Train NS 5621 Utrecht Centraal – Zwolle

Utrecht Centraal 07:21 → Zwolle 08:36 Mon, Tue, Wed, Thu, Fri, Sat 1 h 15 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 07:21 from Utrecht Centraal · Sat 7 Nov

Full trip card
Next departure 07:21 today · Utrecht Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 10 full · 7 partial · 9 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 10 full · 10 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Wed 4 Nov Max en route +5 min · last fix heading to Wezep +5 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Wezep +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
Utrecht Centraal
07:21on time on time
Utrecht Overvecht
07:25≈ on time ≈ on time
Bilthoven
07:30≈ on time ≈ on time
Den Dolder
07:33≈ on time ≈ on time
Amersfoort Centraal
07:40 / 07:42≈ on time ≈ on time
Amersfoort Schothorst
07:46≈ on time ≈ +1 min
Amersfoort Vathorst
07:49≈ on time ≈ +1 min
Nijkerk
07:54≈ on time ≈ +1 min
Putten
07:59≈ on time ≈ +1 min
Ermelo
08:04≈ on time ≈ +1 min
Harderwijk
08:08≈ on time ≈ +1 min
Nunspeet
08:16≈ on time ≈ +1 min
't Harde
08:22≈ on time ≈ +1 min
Wezep
08:29≈ on time ≈ +2 min
Zwolle
08:36on 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
Fri 6 NovWezep 08:49No data—
Thu 5 NovWezep 08:44No data—
Wed 4 NovWezep 08:49Partial coverage+5 min+5 min
Tue 3 NovWezep 08:44No data—
Mon 2 NovWezep 08:44No data—
Sat 31 OctWezep 08:440 min—
Fri 30 OctWezep 08:44Partial coverage0 min—
Thu 29 OctWezep 08:440 min—
Wed 28 OctWezep 08:51No data—
Tue 27 OctWezep 08:44No data—
Mon 26 OctWezep 08:44Partial coverage0 min—
Sat 24 OctWezep 08:45+1 min+1 min
Fri 23 OctWezep 08:47Partial coverage0 min—
Thu 22 OctWezep 08:45Partial coverage0 min—
Wed 21 OctWezep 08:45No data—
Tue 20 OctWezep 08:44Partial coverage0 min—
Mon 19 OctWezep 08:470 min—
Sun 18 OctWezep 08:45+2 min+3 min
Sat 17 OctWezep 08:430 min—
Fri 16 OctWezep 08:500 min—
Thu 15 OctWezep 08:44No data—
Wed 14 OctWezep 08:460 min—
Tue 13 OctWezep 08:440 min—
Mon 12 OctWezep 08:43No data—
Sat 10 OctWezep 08:47+2 min+10 min
Fri 9 OctWezep 08:44Partial coverage0 min—
Thu 8 OctWezep 08:49Partial coverage+5 min+5 min
Wed 7 OctWezep 08:45Partial coverage+1 min+1 min
Tue 6 OctWezep 08:44Partial coverage0 min—
Mon 5 OctWezep 08:44No data—