Train NS 5645 Utrecht Centraal – Zwolle

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 13:21 from Utrecht Centraal · Thu 5 Nov

Next departure 13:21 today · Utrecht Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 2 full · 10 partial · 17 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 2 full · 12 partial · 74 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
13:21on time on time
13:25— —
13:30— —
13:33— —
13:40 / 13:42— —
13:46— —
13:49— —
13:54— —
13:59— —
14:04— —
14:08— —
14:16— —
14:22— —
14:29— —
14:36— —

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 4 NovWezep 14:44Partial coverage0 min—
Tue 3 NovWezep 14:44No data—
Mon 2 NovWezep 14:44No data—
Sun 1 NovWezep 14:440 min—
Sat 31 OctWezep 14:44Partial coverage0 min—
Fri 30 OctWezep 14:44Partial coverage0 min—
Thu 29 OctWezep 14:44No data—
Wed 28 OctWezep 14:45No data—
Tue 27 OctWezep 14:44Partial coverage0 min—
Mon 26 OctWezep 14:44No data—
Sun 25 OctWezep 14:45No data—
Sat 24 OctWezep 14:43Partial coverage0 min—
Fri 23 OctWezep 14:44No data—
Thu 22 OctWezep 14:45No data—
Wed 21 OctWezep 14:44No data—
Tue 20 OctWezep 14:44No data—
Mon 19 OctWezep 15:03No data—
Sun 18 OctWezep 14:430 min—
Sat 17 OctWezep 14:44No data—
Fri 16 OctWezep 14:43No data—
Thu 15 OctWezep 14:47No data—
Wed 14 OctWezep 14:45No data—
Tue 13 OctWezep 14:43No data—
Mon 12 OctWezep 14:42No data—
Sun 11 OctWezep 14:44Partial coverage+1 min+2 min
Sat 10 OctWezep 14:44Partial coverage0 min—
Fri 9 OctWezep 14:44Partial coverage0 min—
Thu 8 OctWezep 14:44Partial coverage0 min—
Wed 7 OctWezep 14:44Partial coverage0 min—
Tue 6 OctWezep 14:44Partial coverage0 min—