Train NS 5653 Utrecht Centraal – Zwolle

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 15:21 from Utrecht Centraal · Sat 7 Nov

Next departure 15:21 today · Utrecht Centraal
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 4 full · 10 partial · 15 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 4 full · 14 partial · 70 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

Worst days

  • Sat 24 Oct Max en route +8 min · last fix heading to Wezep +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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