Train NS 5660 Zwolle – Utrecht Centraal

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

✓ Today’s run finished

Today, last fix heading to Utrecht Overvecht at 18:19 0 min

  1. Zwolle16:53
  2. 't Harde17:06
  3. Ermelo17:24
  4. Nijkerk17:35
  5. Amersfoort Schothorst17:43
  6. Utrecht Overvecht18:05
  7. Utrecht Centraal18:09

Next service: tomorrow 16:53 from Zwolle · Thu 12 Nov

Next departure 16:53 tomorrow · Zwolle
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 7 full · 8 partial · 15 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 11 full · 12 partial · 66 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

  • Mon 26 Oct Max en route +3 min · last fix heading to Utrecht Overvecht +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
16:53on time on time
17:00≈ on time ≈ on time
17:06≈ on time ≈ on time
17:13≈ on time ≈ on time
17:20≈ on time ≈ on time
17:24≈ on time ≈ on time
17:29≈ on time ≈ on time
17:35≈ on time ≈ on time
17:39≈ on time ≈ on time
17:43≈ on time ≈ on time
17:47 / 17:49≈ on time ≈ on time
17:56≈ on time ≈ on time
18:00≈ on time ≈ on time
18:05≈ on time ≈ on time
18:09on 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
Wed 11 NovUtrecht Overvecht 18:19Partial coverage0 min—
Tue 10 NovUtrecht Overvecht 18:19Partial coverage0 min—
Mon 9 NovUtrecht Overvecht 18:19Partial coverage0 min—
Sun 8 NovUtrecht Overvecht 18:190 min—
Sat 7 NovUtrecht Overvecht 18:190 min—
Fri 6 NovUtrecht Overvecht 18:190 min—
Thu 5 NovAmersfoort Centraal 18:29Partial coverage0 min—
Wed 4 NovUtrecht Overvecht 18:19No data—
Tue 3 NovUtrecht Overvecht 18:19No data—
Mon 2 NovUtrecht Overvecht 18:19No data—
Sun 1 NovUtrecht Overvecht 18:190 min—
Sat 31 OctUtrecht Overvecht 18:19No data—
Fri 30 OctUtrecht Overvecht 18:19No data—
Thu 29 OctBilthoven 18:14No data—
Wed 28 OctUtrecht Overvecht 18:19No data—
Tue 27 OctUtrecht Overvecht 18:19No data—
Mon 26 OctUtrecht Overvecht 18:19Partial coverage+3 min+3 min
Sun 25 OctUtrecht Overvecht 18:19No data—
Sat 24 OctUtrecht Overvecht 18:190 min—
Fri 23 OctUtrecht Overvecht 18:20No data—
Thu 22 OctUtrecht Overvecht 18:19Partial coverage0 min—
Wed 21 OctUtrecht Overvecht 18:19No data—
Tue 20 OctUtrecht Overvecht 18:19Partial coverage0 min—
Mon 19 OctUtrecht Overvecht 18:19Partial coverage0 min—
Sun 18 OctErmelo 17:440 min—
Sat 17 OctErmelo 17:45No data—
Fri 16 OctUtrecht Overvecht 18:200 min—
Thu 15 OctUtrecht Overvecht 18:20No data—
Wed 14 OctUtrecht Overvecht 18:20No data—
Tue 13 OctUtrecht Overvecht 18:20No data—