Train NS 5673 Utrecht Centraal – Zwolle

Utrecht Centraal 20:20 → Zwolle 21:36 Daily 1 h 16 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 20:20 from Utrecht Centraal · Sun 8 Nov

Full trip card
Next departure 20:20 today · Utrecht Centraal
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 18 full · 3 partial · 8 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 23 full · 3 partial · 28 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

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

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

On-time by weekday

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

Stops and timetable

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

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