Train NS 5625 Utrecht Centraal – Zwolle

Utrecht Centraal 08:20 → Zwolle 09:36 Daily 1 h 16 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Utrecht Centraal08:20
  2. Bilthoven08:31
  3. Amersfoort Schothorst08:46
  4. Nijkerk08:54
  5. Ermelo09:04
  6. Wezep09:29
  7. Zwolle09:36

Next service: tomorrow 08:20 from Utrecht Centraal · Sun 8 Nov

Next departure 08:20 tomorrow · Utrecht Centraal
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 16 full · 4 partial · 10 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 19 full · 4 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

Worst days

  • Wed 4 Nov Max en route +5 min · last fix heading to Wezep +5 min

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 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
08:20on time on time
08:24≈ on time ≈ on time
08:31≈ on time ≈ on time
08:34≈ on time ≈ on time
08:40 / 08:42≈ on time ≈ on time
08:46≈ on time ≈ on time
08:49≈ on time ≈ on time
08:54≈ on time ≈ on time
08:59≈ on time ≈ on time
09:04≈ on time ≈ on time
09:08≈ on time ≈ on time
09:16≈ on time ≈ +1 min
09:22≈ on time ≈ +1 min
09:29≈ on time ≈ +1 min
09:36on 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
Sat 7 NovWezep 09:44Partial coverage0 min—
Fri 6 NovWezep 09:44No data—
Thu 5 NovWezep 09:44No data—
Wed 4 NovWezep 09:48+5 min+5 min
Tue 3 NovWezep 09:49No data—
Mon 2 NovWezep 09:44No data—
Sun 1 NovWezep 09:440 min—
Sat 31 OctWezep 09:44Partial coverage0 min—
Fri 30 OctWezep 09:440 min—
Thu 29 OctWezep 09:450 min—
Wed 28 OctWezep 09:44No data—
Tue 27 OctWezep 09:440 min—
Mon 26 OctWezep 09:44No data—
Sun 25 OctWezep 09:44No data—
Sat 24 OctWezep 09:45+1 min+1 min
Fri 23 OctWezep 09:450 min—
Thu 22 OctWezep 09:480 min—
Wed 21 OctWezep 09:440 min—
Tue 20 OctWezep 09:440 min—
Mon 19 OctWezep 09:440 min—
Sun 18 OctWezep 09:430 min—
Sat 17 OctWezep 09:430 min—
Fri 16 OctWezep 09:420 min—
Thu 15 OctWezep 10:58No data—
Wed 14 OctWezep 09:43No data—
Tue 13 OctWezep 09:42No data—
Mon 12 OctWezep 09:430 min—
Sun 11 OctWezep 09:44Partial coverage0 min—
Sat 10 OctWezep 09:44Partial coverage0 min—
Fri 9 OctWezep 09:450 min—