Train NS 5623 Utrecht Centraal – Zwolle

Utrecht Centraal 07:51 → Zwolle 09:06 Daily 1 h 15 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Wezep at 09:14 0 min

  1. Utrecht Centraal07:51
  2. Bilthoven08:00
  3. Amersfoort Schothorst08:16
  4. Nijkerk08:24
  5. Ermelo08:34
  6. Wezep08:59
  7. Zwolle09:06

Next service: tomorrow 07:51 from Utrecht Centraal · Sat 21 Nov

Next departure 07:51 tomorrow · Utrecht Centraal
On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 7 full · 18 partial · 5 no data
On-time · 90 days
92%
34/37 runs under 3 min
RT coverage: 13 full · 24 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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 1 Nov Max en route +6 min · last fix heading to Wezep +6 min
  • Wed 7 Oct Max en route +7 min · last fix heading to Wezep +5 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Wezep +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 34
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 67% W n=6
  • 100% T n=5
  • 100% F n=5
  • 100% S n=6
  • 75% S n=4

Stops and timetable

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

Last 90 days, 37 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
07:51on time on time
07:55≈ on time ≈ on time
08:00≈ on time ≈ on time
08:03≈ on time ≈ on time
08:10 / 08:12≈ on time ≈ on time
08:16≈ on time ≈ on time
08:19≈ on time ≈ on time
08:24≈ on time ≈ on time
08:29≈ on time ≈ on time
08:34≈ on time ≈ on time
08:38≈ on time ≈ on time
08:46≈ on time ≈ +1 min
08:52≈ on time ≈ +1 min
08:59≈ on time ≈ +1 min
09: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 20 NovWezep 09:14Partial coverage0 min—
Thu 19 NovWezep 09:14Partial coverage+1 min+3 min
Wed 18 NovWezep 09:14Partial coverage0 min—
Tue 17 NovWezep 09:14Partial coverage+1 min+2 min
Mon 16 NovWezep 09:17Partial coverage+2 min+2 min
Sun 15 NovWezep 09:14+1 min+1 min
Sat 14 NovWezep 09:140 min—
Fri 13 NovWezep 09:17Partial coverage+2 min+2 min
Thu 12 NovWezep 09:14Partial coverage0 min—
Wed 11 NovWezep 09:14Partial coverage0 min—
Tue 10 NovWezep 09:14Partial coverage+2 min+2 min
Mon 9 NovWezep 09:14Partial coverage+1 min+1 min
Sun 8 NovWezep 09:140 min—
Sat 7 NovWezep 09:140 min—
Fri 6 NovWezep 09:14No data—
Thu 5 NovWezep 09:14No data—
Wed 4 NovWezep 09:17Partial coverage+3 min+3 min
Tue 3 NovWezep 09:14No data—
Mon 2 NovWezep 09:14Partial coverage0 min—
Sun 1 NovWezep 09:21+6 min+6 min
Sat 31 OctWezep 09:140 min—
Fri 30 OctWezep 09:14No data—
Thu 29 OctWezep 09:14Partial coverage0 min—
Wed 28 OctWezep 09:14Partial coverage0 min—
Tue 27 OctWezep 09:14Partial coverage0 min—
Mon 26 OctWezep 09:15Partial coverage0 min—
Sun 25 OctWezep 09:14No data—
Sat 24 OctWezep 09:140 min—
Fri 23 OctWezep 09:14Partial coverage0 min—
Thu 22 OctWezep 09:14Partial coverage0 min—