Train NS 5665 Utrecht Centraal – Zwolle

Utrecht Centraal 18:21 → Zwolle 19: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 18:21 from Utrecht Centraal · Wed 11 Nov

Next departure 18:21 today · Utrecht Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 10 full · 7 partial · 12 no data
On-time · 90 days
96%
24/25 runs under 3 min
RT coverage: 15 full · 10 partial · 45 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

  • Mon 2 Nov Max en route +12 min · last fix heading to Utrecht Centraal +12 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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
18:21on time on time
18:25≈ on time ≈ on time
18:30≈ on time ≈ on time
18:33≈ on time ≈ on time
18:40 / 18:42≈ on time ≈ on time
18:46≈ on time ≈ on time
18:49≈ on time ≈ on time
18:54≈ on time ≈ on time
18:59≈ on time ≈ on time
19:04≈ on time ≈ on time
19:08≈ on time ≈ on time
19:16≈ on time ≈ on time
19:22≈ on time ≈ on time
19:29≈ on time ≈ on time
19: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 NovUtrecht Centraal 19:380 min—
Mon 9 Nov— 19:380 min—
Sun 8 NovWezep 19:440 min—
Sat 7 NovWezep 19:44Partial coverage0 min—
Fri 6 NovAmersfoort Schothorst 19:37Partial coverage0 min—
Thu 5 Nov— 19:37No data—
Wed 4 Nov— 19:38No data—
Tue 3 Nov— 19:37No data—
Mon 2 NovUtrecht Centraal 20:28Partial coverage+12 min+12 min
Sun 1 NovWezep 19:44Partial coverage0 min—
Sat 31 OctWezep 19:44Partial coverage0 min—
Fri 30 OctNijkerk 19:08No data—
Thu 29 Oct— 19:380 min—
Wed 28 Oct— 19:400 min—
Tue 27 Oct— 19:420 min—
Mon 26 Oct— 19:37No data—
Sun 25 OctWezep 19:44No data—
Sat 24 OctWezep 19:54No data—
Fri 23 Oct't Harde 19:37Partial coverage0 min+1 min
Thu 22 OctAmersfoort Centraal 19:38No data—
Wed 21 OctDen Dolder 19:40No data—
Tue 20 OctAmersfoort Schothorst 19:370 min—
Mon 19 OctAmersfoort Centraal 19:37Partial coverage0 min—
Sun 18 OctWezep 19:430 min—
Sat 17 OctWezep 19:430 min—
Fri 16 OctWezep 19:42No data—
Thu 15 OctBilthoven 19:36No data—
Wed 14 OctWezep 19:420 min—
Tue 13 OctAmersfoort Centraal 19:47No data—
Mon 12 OctAmersfoort Schothorst 19:360 min—