Train NS 5629 Utrecht Centraal – Zwolle

Utrecht Centraal 09:21 → Zwolle 10:36 Daily 1 h 15 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Wezep at 10:44 +1 min

  1. Utrecht Centraal09:21
  2. Bilthoven09:30
  3. Amersfoort Schothorst09:46
  4. Nijkerk09:54
  5. Ermelo10:04
  6. Wezep10:29
  7. Zwolle10:36

Next service: tomorrow 09:21 from Utrecht Centraal · Thu 12 Nov

Next departure 09:21 tomorrow · Utrecht Centraal
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 6 full · 15 partial · 9 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 8 full · 19 partial · 62 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: +1 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

  • Tue 10 Nov Max en route +19 min · last fix heading to Wezep +14 min
  • Sat 31 Oct Max en route +6 min · last fix heading to Wezep +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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