Train NS 5670 Zwolle – Utrecht Centraal

Zwolle 19:23 → Utrecht Centraal 20:39 Daily 1 h 16 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 19:23 from Zwolle · Fri 6 Nov

Full trip card
Next departure 19:23 today · Zwolle
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 10 full · 5 partial · 12 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 13 full · 5 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +11 min

Last 30 days

Arrival delay at Utrecht Centraal, 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 +28 min · last fix heading to Amersfoort Centraal +28 min
  • Sun 18 Oct Max en route +17 min · last fix heading to Ermelo +17 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 0% · 0
  • 10–30 min 11% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
Zwolle
19:23on time on time
Wezep
19:30≈ on time ≈ on time
't Harde
19:36≈ on time ≈ on time
Nunspeet
19:42≈ on time ≈ on time
Harderwijk
19:50≈ on time ≈ on time
Ermelo
19:54≈ on time ≈ on time
Putten
19:59≈ on time ≈ on time
Nijkerk
20:04≈ on time ≈ on time
Amersfoort Vathorst
20:09≈ on time ≈ on time
Amersfoort Schothorst
20:12≈ on time ≈ on time
Amersfoort Centraal
20:16 / 20:19≈ on time ≈ on time
Den Dolder
20:26≈ on time ≈ +1 min
Bilthoven
20:30≈ on time ≈ +1 min
Utrecht Overvecht
20:35≈ on time ≈ +1 min
Utrecht Centraal
20:39on 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
Thu 5 Nov— 20:39No data—
Wed 4 Nov— 20:390 min—
Tue 3 Nov— 20:47No data—
Sun 1 NovUtrecht Overvecht 20:49Partial coverage0 min—
Sat 31 OctUtrecht Overvecht 20:49Partial coverage0 min—
Thu 29 Oct— 20:410 min—
Wed 28 Oct— 20:400 min—
Tue 27 Oct— 20:410 min—
Mon 26 OctHarderwijk 20:43No data—
Sun 25 OctUtrecht Overvecht 20:52No data—
Sat 24 OctUtrecht Overvecht 20:51No data—
Fri 23 OctZwolle 20:44Partial coverage+2 min+2 min
Thu 22 Oct— 20:43No data—
Wed 21 Oct— 20:40No data—
Tue 20 Oct— 20:40No data—
Mon 19 Oct— 20:410 min—
Sun 18 OctErmelo 20:32+17 min+17 min
Sat 17 OctErmelo 20:14No data—
Fri 16 OctErmelo 20:42+1 min—
Thu 15 Oct— 20:43No data—
Wed 14 OctNunspeet 20:41No data—
Tue 13 Oct— 20:42No data—
Mon 12 Oct— 20:420 min—
Sun 11 OctAmersfoort Centraal 21:27Partial coverage+28 min+28 min
Sat 10 OctUtrecht Overvecht 20:49Partial coverage0 min—
Fri 9 Oct— 20:400 min—
Thu 8 Oct— 23:470 min—
Wed 7 Oct— 20:400 min—
Tue 6 Oct— 20:400 min+1 min
Mon 5 Oct— 20:410 min—