Train NS 5675 Utrecht Centraal – Zwolle

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

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 20:50 from Utrecht Centraal · Sat 14 Nov

Full trip card
Next departure 20:50 today · Utrecht Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 15 full · 3 partial · 9 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 23 full · 3 partial · 24 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: +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 +20 min · last fix heading to Nijkerk +20 min

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 96% · 25
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

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:50on time on time
Utrecht Overvecht
20:54≈ on time ≈ on time
Bilthoven
21:01≈ on time ≈ on time
Den Dolder
21:04≈ on time ≈ on time
Amersfoort Centraal
21:10 / 21:12≈ on time ≈ on time
Amersfoort Schothorst
21:16≈ on time ≈ on time
Amersfoort Vathorst
21:19≈ on time ≈ on time
Nijkerk
21:24≈ on time ≈ on time
Putten
21:29≈ on time ≈ on time
Ermelo
21:34≈ on time ≈ +1 min
Harderwijk
21:38≈ on time ≈ +1 min
Nunspeet
21:46≈ on time ≈ +1 min
't Harde
21:52≈ on time ≈ +1 min
Wezep
21:59≈ on time ≈ +1 min
Zwolle
22:06on time +1 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 13 Nov— 21:090 min—
Thu 12 Nov— 22:070 min—
Wed 11 Nov— 22:070 min—
Tue 10 Nov— 22:070 min—
Mon 9 Nov— 22:080 min+1 min
Sun 8 NovWezep 22:14Partial coverage0 min+2 min
Sat 7 NovWezep 22:13Partial coverage0 min—
Fri 6 Nov— 22:090 min+2 min
Thu 5 Nov— 22:08No data—
Wed 4 Nov— 22:070 min—
Mon 2 Nov— 22:08+1 min+1 min
Sun 1 NovWezep 22:14Partial coverage0 min—
Sat 31 OctWezep 22:17No data—
Thu 29 Oct— 22:070 min—
Wed 28 Oct— 22:070 min—
Tue 27 Oct— 22:100 min—
Mon 26 Oct— 22:07No data—
Sun 25 OctWezep 22:15No data—
Sat 24 OctWezep 22:18No data—
Fri 23 Oct— 22:080 min—
Thu 22 Oct— 22:08No data—
Wed 21 Oct— 22:08No data—
Tue 20 Oct— 22:08No data—
Mon 19 Oct— 22:080 min—
Sun 18 OctWezep 22:120 min—
Sat 17 OctWezep 22:13No data—
Fri 16 Oct— 22:07+1 min+1 min
Thu 15 Oct— 22:08No data—
Wed 14 Oct— 22:06No data—
Tue 13 Oct— 22:07No data—