Train NS 5641 Utrecht Centraal – Zwolle

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

✓ Today’s run finished

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

  1. Utrecht Centraal12:21
  2. Bilthoven12:30
  3. Amersfoort Schothorst12:46
  4. Nijkerk12:54
  5. Ermelo13:04
  6. Wezep13:29
  7. Zwolle13:36

Next service: tomorrow 12:21 from Utrecht Centraal · Tue 10 Nov

Next departure 12:21 tomorrow · Utrecht Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 5 full · 14 partial · 11 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 5 full · 20 partial · 64 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=4
  • 100% T n=3
  • 100% F n=3
  • 100% 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, 25 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
12:21on time on time
12:25≈ on time ≈ on time
12:30≈ on time ≈ on time
12:33≈ on time ≈ on time
12:40 / 12:42≈ on time ≈ on time
12:46≈ on time ≈ on time
12:49≈ on time ≈ on time
12:54≈ on time ≈ on time
12:59≈ on time ≈ on time
13:04≈ on time ≈ on time
13:08≈ on time ≈ on time
13:16≈ on time ≈ on time
13:22≈ on time ≈ on time
13:29≈ on time ≈ on time
13: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
Mon 9 NovWezep 13:44Partial coverage0 min+3 min
Sun 8 NovWezep 13:43Partial coverage0 min+2 min
Sat 7 NovWezep 13:44Partial coverage0 min—
Fri 6 NovWezep 13:44No data—
Thu 5 NovWezep 13:43No data—
Wed 4 NovWezep 13:44Partial coverage+1 min+1 min
Tue 3 NovWezep 13:44Partial coverage0 min—
Mon 2 NovWezep 13:44Partial coverage0 min—
Sun 1 NovWezep 13:440 min—
Sat 31 OctWezep 13:44Partial coverage+1 min+3 min
Fri 30 OctWezep 13:44No data—
Thu 29 OctWezep 13:44Partial coverage0 min—
Wed 28 OctWezep 13:43No data—
Tue 27 OctWezep 13:44No data—
Mon 26 OctWezep 13:44No data—
Sun 25 OctWezep 13:45No data—
Sat 24 OctWezep 13:44Partial coverage0 min—
Fri 23 OctWezep 13:44Partial coverage0 min—
Thu 22 OctWezep 13:44Partial coverage0 min—
Wed 21 OctWezep 13:46Partial coverage0 min—
Tue 20 OctWezep 13:44No data—
Mon 19 OctWezep 13:44Partial coverage0 min—
Sun 18 OctWezep 13:430 min—
Sat 17 OctWezep 13:430 min—
Fri 16 OctWezep 13:460 min—
Thu 15 OctWezep 13:42No data—
Wed 14 OctWezep 13:420 min—
Tue 13 OctWezep 13:46No data—
Mon 12 OctWezep 13:42No data—
Sun 11 OctWezep 13:44Partial coverage+1 min+1 min