Train NS 5649 Utrecht Centraal – Zwolle

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

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 14:21 from Utrecht Centraal · Wed 11 Nov

Next departure 14:21 today · Utrecht Centraal
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 4 full · 14 partial · 11 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 7 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: +2 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

  • Wed 4 Nov Max en route +8 min · last fix heading to Den Dolder +8 min
  • Sun 1 Nov Max en route +8 min · last fix heading to Wezep +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 24
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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