Train NS 5684 Zwolle – Utrecht Centraal

Zwolle 22:53 → Utrecht Centraal 00:09 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 22:53 from Zwolle · Fri 6 Nov

Full trip card
Next departure 22:53 today · Zwolle
On-time · 30 days
86%
18/21 runs under 3 min
RT coverage: 19 full · 2 partial · 6 no data
On-time · 90 days
88%
21/24 runs under 3 min
RT coverage: 21 full · 3 partial · 22 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

  • Thu 8 Oct Max en route +13 min · last fix heading to — +13 min
  • Fri 23 Oct Max en route +6 min · last fix heading to — +6 min
  • Mon 12 Oct Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 21
  • 3–10 min 8% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
22:53on time on time
Wezep
23:00≈ on time ≈ +1 min
't Harde
23:07≈ on time ≈ +1 min
Nunspeet
23:13≈ on time ≈ +1 min
Harderwijk
23:21≈ on time ≈ +1 min
Ermelo
23:25≈ on time ≈ +1 min
Putten
23:30≈ on time ≈ +2 min
Nijkerk
23:35≈ on time ≈ +2 min
Amersfoort Vathorst
23:39≈ on time ≈ +2 min
Amersfoort Schothorst
23:43≈ on time ≈ +2 min
Amersfoort Centraal
23:46 / 23:49≈ on time ≈ +2 min
Den Dolder
23:56≈ on time ≈ +3 min
Bilthoven
00:00≈ on time ≈ +3 min
Utrecht Overvecht
00:04 / 00:05≈ on time ≈ +3 min
Utrecht Centraal
00: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
Thu 5 Nov— 00:09No data—
Wed 4 Nov— 00:090 min—
Sun 1 NovUtrecht Overvecht 00:19Partial coverage0 min—
Sat 31 OctHarderwijk 00:23Partial coverage0 min—
Fri 30 Oct— 00:100 min—
Thu 29 Oct— 00:11+3 min+3 min
Wed 28 Oct— 00:100 min—
Tue 27 Oct— 00:130 min—
Mon 26 Oct— 00:110 min—
Sun 25 OctUtrecht Overvecht 00:20No data—
Sat 24 Oct— 00:27No data—
Fri 23 Oct— 00:21+6 min+6 min
Thu 22 Oct— 00:34No data—
Wed 21 Oct— 00:130 min—
Tue 20 Oct— 00:110 min—
Mon 19 Oct— 00:110 min—
Sun 18 OctErmelo 23:44No data—
Sat 17 OctErmelo 23:440 min—
Fri 16 Oct— 00:170 min+6 min
Thu 15 Oct— 00:16No data—
Wed 14 Oct— 00:150 min—
Tue 13 Oct— 00:130 min—
Mon 12 Oct— 00:17+3 min+4 min
Sun 11 OctUtrecht Overvecht 00:190 min—
Sat 10 Oct— 00:110 min—
Fri 9 Oct— 00:100 min—
Thu 8 Oct— 00:24+13 min+13 min
Wed 7 Oct— 00:14+2 min+2 min
Tue 6 Oct— 00:100 min—
Mon 5 OctUtrecht Overvecht 00:11Partial coverage0 min—