Train NS 5626 Zwolle – Utrecht Centraal

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

✓ Today’s run finished

Today, last fix heading to Utrecht Overvecht at 09:49 0 min

  1. Zwolle08:23
  2. 't Harde08:36
  3. Ermelo08:54
  4. Nijkerk09:04
  5. Amersfoort Schothorst09:12
  6. Utrecht Overvecht09:35
  7. Utrecht Centraal09:39

Next service: tomorrow 08:23 from Zwolle · Fri 6 Nov

Next departure 08:23 tomorrow · Zwolle
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 10 full · 8 partial · 12 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 10 full · 9 partial · 68 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 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

  • Fri 9 Oct Max en route +4 min · last fix heading to Utrecht Overvecht +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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:23on time on time
08:30≈ on time ≈ on time
08:36≈ on time ≈ on time
08:42≈ on time ≈ on time
08:50≈ 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:12≈ on time ≈ on time
09:15 / 09:19≈ on time ≈ on time
09:26≈ on time ≈ on time
09:30≈ on time ≈ on time
09:35≈ on time ≈ on time
09:39on 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 NovUtrecht Overvecht 09:49Partial coverage0 min—
Wed 4 NovUtrecht Overvecht 09:49Partial coverage+1 min+2 min
Tue 3 NovUtrecht Overvecht 09:49No data—
Mon 2 NovUtrecht Overvecht 09:49No data—
Sun 1 NovUtrecht Overvecht 09:500 min—
Sat 31 OctUtrecht Overvecht 09:500 min—
Fri 30 OctUtrecht Overvecht 09:49No data—
Thu 29 OctUtrecht Overvecht 09:49No data—
Wed 28 OctUtrecht Overvecht 09:49Partial coverage0 min—
Tue 27 OctUtrecht Overvecht 09:50Partial coverage0 min—
Mon 26 OctUtrecht Overvecht 09:49No data—
Sun 25 OctUtrecht Overvecht 09:50No data—
Sat 24 OctUtrecht Overvecht 09:500 min—
Fri 23 OctUtrecht Overvecht 10:08Partial coverage0 min—
Thu 22 OctUtrecht Overvecht 09:50No data—
Wed 21 OctUtrecht Overvecht 09:53No data—
Tue 20 OctUtrecht Overvecht 09:49No data—
Mon 19 OctUtrecht Overvecht 10:010 min—
Sun 18 OctErmelo 09:14No data—
Sat 17 OctErmelo 09:140 min—
Fri 16 OctUtrecht Overvecht 09:500 min—
Thu 15 OctUtrecht Overvecht 09:51No data—
Wed 14 OctUtrecht Overvecht 09:540 min—
Tue 13 OctUtrecht Overvecht 09:52No data—
Mon 12 OctUtrecht Overvecht 09:490 min—
Sun 11 OctUtrecht Overvecht 09:490 min—
Sat 10 OctUtrecht Overvecht 09:500 min—
Fri 9 OctUtrecht Overvecht 09:54Partial coverage+4 min+4 min
Thu 8 OctUtrecht Overvecht 09:50Partial coverage+1 min+1 min
Wed 7 OctUtrecht Overvecht 09:49Partial coverage0 min—