Train NS 5683 Utrecht Centraal – Zwolle

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

Full trip card
Next departure 22:50 today · Utrecht Centraal
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 18 full · 2 partial · 7 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 20 full · 3 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 23
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
22:50on time on time
Utrecht Overvecht
22:54≈ on time ≈ on time
Bilthoven
23:01≈ on time ≈ on time
Den Dolder
23:04≈ on time ≈ on time
Amersfoort Centraal
23:10 / 23:12≈ on time ≈ on time
Amersfoort Schothorst
23:16≈ on time ≈ on time
Amersfoort Vathorst
23:19≈ on time ≈ on time
Nijkerk
23:24≈ on time ≈ on time
Putten
23:29≈ on time ≈ on time
Ermelo
23:34≈ on time ≈ on time
Harderwijk
23:38≈ on time ≈ on time
Nunspeet
23:46≈ on time ≈ on time
't Harde
23:52≈ on time ≈ on time
Wezep
23:59≈ on time ≈ on time
Zwolle
00:06on time on time

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:07No data—
Wed 4 Nov— 23:120 min—
Mon 2 Nov— 00:070 min—
Sun 1 NovWezep 00:14Partial coverage0 min—
Sat 31 OctAmersfoort Vathorst 00:07No data—
Fri 30 Oct— 00:07No data—
Wed 28 Oct— 00:070 min—
Tue 27 Oct— 00:070 min—
Mon 26 Oct— 00:070 min—
Sun 25 OctWezep 00:13Partial coverage0 min—
Sat 24 Oct— 00:35No data—
Fri 23 Oct— 00:080 min—
Thu 22 Oct— 00:07No data—
Wed 21 Oct— 00:07No data—
Tue 20 Oct— 00:070 min—
Mon 19 Oct— 00:080 min—
Sun 18 OctWezep 00:130 min—
Sat 17 OctWezep 00:13No data—
Fri 16 Oct— 00:060 min—
Thu 15 Oct— 00:080 min—
Wed 14 Oct— 00:060 min—
Tue 13 Oct— 00:070 min—
Mon 12 Oct— 23:100 min—
Sun 11 OctNijkerk 23:380 min—
Sat 10 Oct— 00:080 min—
Fri 9 Oct— 00:070 min—
Thu 8 Oct— 00:080 min—
Wed 7 Oct— 00:070 min—
Tue 6 Oct— 00:070 min—
Mon 5 OctNunspeet 00:07Partial coverage0 min—