Train NS 5679 Utrecht Centraal – Zwolle

Utrecht Centraal 21:50 → Zwolle 23:06 Daily 1 h 16 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 9 November +6 min

Next service: today 21:50 from Utrecht Centraal · Tue 10 Nov

Next departure 21:50 today · Utrecht Centraal
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 16 full · 2 partial · 9 no data
On-time · 90 days
84%
21/25 runs under 3 min
RT coverage: 23 full · 2 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sun 11 Oct Max en route +13 min · last fix heading to Nijkerk +13 min
  • Wed 7 Oct Max en route +10 min · last fix heading to — +10 min
  • Mon 9 Nov Max en route +6 min · last fix heading to — +6 min
  • Mon 12 Oct Max en route +4 min · last fix heading to — +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 84% · 21
  • 3–10 min 8% · 2
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (15 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
21:50on time on time
21:54≈ on time ≈ on time
22:01≈ on time ≈ +1 min
22:04≈ on time ≈ +1 min
22:10 / 22:12≈ on time ≈ +1 min
22:16≈ on time ≈ +2 min
22:19≈ on time ≈ +2 min
22:24≈ on time ≈ +2 min
22:29≈ on time ≈ +3 min
22:34≈ on time ≈ +3 min
22:38≈ on time ≈ +3 min
22:46≈ on time ≈ +4 min
22:52≈ on time ≈ +4 min
22:59≈ on time ≈ +5 min
23:06on time +5 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
Mon 9 Nov— 23:12+6 min+6 min
Sun 8 NovWezep 23:14Partial coverage0 min—
Sat 7 NovWezep 23:13Partial coverage0 min—
Fri 6 Nov— 23:070 min—
Thu 5 Nov— 23:08No data—
Wed 4 Nov— 23:070 min—
Mon 2 Nov— 23:070 min—
Sun 1 NovWezep 23:140 min—
Sat 31 OctWezep 23:130 min—
Fri 30 Oct— 23:07No data—
Wed 28 Oct— 23:070 min—
Tue 27 Oct— 23:080 min—
Mon 26 Oct— 23:12No data—
Sun 25 OctWezep 23:14No data—
Sat 24 OctHarderwijk 23:07No data—
Fri 23 Oct— 23:080 min—
Thu 22 Oct— 23:08No data—
Wed 21 Oct— 23:07No data—
Tue 20 Oct— 23:070 min—
Mon 19 Oct— 23:08No data—
Sun 18 OctWezep 23:130 min—
Sat 17 OctWezep 23:13No data—
Fri 16 Oct— 23:060 min—
Thu 15 Oct— 23:070 min—
Wed 14 Oct— 23:060 min—
Tue 13 Oct— 23:060 min—
Mon 12 Oct— 23:15+4 min+4 min
Sun 11 OctNijkerk 22:51+13 min+13 min
Sat 10 OctDen Dolder 23:12+2 min+2 min
Fri 9 Oct— 23:070 min—