Train NS 5672 Zwolle – Utrecht Centraal

Zwolle 19:53 → Utrecht Centraal 21:09 Daily 1 h 16 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +3 min

Next service: today 19:53 from Zwolle · Thu 5 Nov

Next departure 19:53 today · Zwolle
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 14 full · 5 partial · 9 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 16 full · 5 partial · 33 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: +3 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

  • Mon 2 Nov Max en route +14 min · last fix heading to — +13 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Utrecht Overvecht +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 19
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
19:53on time on time
20:00≈ on time ≈ on time
20:06≈ on time ≈ on time
20:12≈ on time ≈ +1 min
20:20≈ on time ≈ +1 min
20:24≈ on time ≈ +1 min
20:29≈ on time ≈ +1 min
20:34≈ on time ≈ +1 min
20:39≈ on time ≈ +2 min
20:42≈ on time ≈ +2 min
20:46 / 20:49≈ on time ≈ +2 min
20:56≈ on time ≈ +2 min
21:00≈ on time ≈ +2 min
21:05≈ on time ≈ +2 min
21:09on time +3 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
Wed 4 Nov— 21:14+3 min+3 min
Tue 3 Nov— 21:140 min—
Mon 2 Nov— 21:24+13 min+14 min
Sun 1 NovUtrecht Overvecht 21:19Partial coverage0 min—
Sat 31 OctUtrecht Overvecht 21:19Partial coverage0 min—
Thu 29 Oct— 21:15+2 min+3 min
Wed 28 Oct— 21:10No data—
Tue 27 Oct— 21:11No data—
Mon 26 Oct— 21:140 min—
Sun 25 OctUtrecht Overvecht 21:19No data—
Sat 24 OctUtrecht Overvecht 21:22Partial coverage0 min—
Fri 23 Oct— 21:11+1 min+1 min
Thu 22 Oct— 21:110 min—
Wed 21 Oct— 21:12No data—
Tue 20 Oct— 21:19No data—
Mon 19 Oct— 21:130 min—
Sun 18 OctErmelo 20:440 min—
Sat 17 OctErmelo 20:44No data—
Fri 16 OctZwolle 03:25+1 min+1 min
Thu 15 Oct— 21:20No data—
Wed 14 Oct— 21:11No data—
Tue 13 Oct— 21:12No data—
Mon 12 Oct— 21:110 min—
Sun 11 OctUtrecht Overvecht 21:22Partial coverage+3 min+5 min
Sat 10 OctUtrecht Overvecht 21:19Partial coverage0 min—
Fri 9 Oct— 21:100 min—
Thu 8 Oct— 21:170 min—
Wed 7 Oct— 21:110 min—
Tue 6 Oct— 21:100 min—
Mon 5 Oct— 21:100 min—