Train NS 5644 Zwolle – Utrecht Centraal

Zwolle 12:53 → Utrecht Centraal 14:09 Daily 1 h 16 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +6 min

Next service: today 12:53 from Zwolle · Thu 5 Nov

Next departure 12:53 today · Zwolle
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 7 full · 11 partial · 11 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 7 full · 13 partial · 68 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 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

  • Wed 4 Nov Max en route +6 min · last fix heading to Utrecht Overvecht +6 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 67% W n=3
  • 100% T n=2
  • 100% F n=4
  • 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, 20 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:53on time on time
13:00≈ on time ≈ on time
13:06≈ on time ≈ on time
13:12≈ on time ≈ on time
13:20≈ on time ≈ on time
13:24≈ on time ≈ on time
13:29≈ on time ≈ on time
13:34≈ on time ≈ on time
13:39≈ on time ≈ on time
13:42≈ on time ≈ on time
13:46 / 13:49≈ on time ≈ on time
13:56≈ on time ≈ on time
14:00≈ on time ≈ on time
14:05≈ on time ≈ on time
14:09on time +1 min

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 NovUtrecht Overvecht 14:24Partial coverage+6 min+6 min
Tue 3 NovUtrecht Overvecht 14:19No data—
Mon 2 NovUtrecht Overvecht 14:19No data—
Sun 1 NovUtrecht Overvecht 14:200 min—
Sat 31 OctUtrecht Overvecht 14:19Partial coverage0 min—
Fri 30 OctUtrecht Overvecht 14:19Partial coverage0 min—
Thu 29 OctUtrecht Overvecht 14:19No data—
Wed 28 OctUtrecht Overvecht 14:19Partial coverage0 min—
Tue 27 OctUtrecht Overvecht 14:19Partial coverage0 min—
Mon 26 OctUtrecht Overvecht 14:19No data—
Sun 25 OctUtrecht Overvecht 14:19No data—
Sat 24 OctUtrecht Overvecht 14:19Partial coverage0 min—
Fri 23 OctUtrecht Overvecht 14:270 min—
Thu 22 OctUtrecht Overvecht 14:22No data—
Wed 21 OctUtrecht Overvecht 14:19No data—
Tue 20 OctUtrecht Overvecht 14:20No data—
Mon 19 OctUtrecht Overvecht 14:19Partial coverage0 min—
Sun 18 OctErmelo 13:45+1 min+1 min
Sat 17 OctErmelo 13:44No data—
Fri 16 OctUtrecht Overvecht 14:200 min—
Thu 15 OctUtrecht Overvecht 14:200 min—
Wed 14 OctUtrecht Overvecht 14:21No data—
Tue 13 OctUtrecht Overvecht 14:20No data—
Mon 12 OctUtrecht Overvecht 14:210 min—
Sun 11 OctUtrecht Overvecht 14:190 min—
Sat 10 OctUtrecht Overvecht 14:19Partial coverage0 min—
Fri 9 OctUtrecht Overvecht 14:19Partial coverage0 min—
Thu 8 OctUtrecht Overvecht 14:19Partial coverage0 min+1 min
Wed 7 OctUtrecht Overvecht 14:19Partial coverage0 min—
Tue 6 OctUtrecht Overvecht 14:19Partial coverage0 min—