Train NS 5687 Utrecht Centraal – Zwolle

Utrecht Centraal 23:50 → Zwolle 01:06 Daily 1 h 16 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 23:50 from Utrecht Centraal · Fri 20 Nov

Next departure 23:50 today · Utrecht Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 17 full · 1 partial · 2 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 31 full · 1 partial · 9 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 19 Oct Max en route +8 min · last fix heading to — +6 min
  • Fri 16 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 32 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
23:50on time on time
23:54≈ on time ≈ on time
00:01≈ on time ≈ on time
00:04≈ on time ≈ on time
00:10 / 00:12≈ on time ≈ on time
00:16≈ on time ≈ on time
00:19≈ on time ≈ on time
00:24≈ on time ≈ on time
00:29≈ on time ≈ on time
00:34≈ on time ≈ on time
00:38≈ on time ≈ on time
00:46≈ on time ≈ on time
00:52≈ on time ≈ on time
00:59≈ on time ≈ on time
01:06on 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
Thu 19 Nov— 01:090 min—
Wed 18 Nov— 01:070 min—
Tue 17 Nov— 01:080 min—
Mon 16 Nov— 01:070 min—
Sun 15 NovWezep 01:140 min—
Sat 14 Nov— 01:070 min—
Wed 11 Nov— 01:070 min—
Fri 6 NovWezep 06:24Partial coverage0 min+1 min
Thu 5 Nov— 01:07No data—
Wed 4 Nov— 01:080 min—
Sun 1 NovWezep 01:140 min—
Sat 31 Oct— 01:070 min—
Thu 29 Oct— 01:070 min—
Wed 28 Oct— 01:070 min—
Tue 27 Oct— 01:070 min—
Mon 26 Oct— 01:070 min—
Sun 25 OctWezep 01:15No data—
Sat 24 Oct— 01:080 min—
Fri 23 Oct— 01:080 min—
Thu 22 Oct— 01:070 min—
Wed 21 Oct— 01:070 min—
Tue 20 Oct— 01:120 min—
Mon 19 Oct— 01:20+6 min+8 min
Fri 16 Oct— 01:13+4 min+4 min
Thu 15 Oct— 01:060 min—
Wed 14 Oct— 01:060 min—
Mon 12 Oct— 01:060 min—
Sun 11 OctNijkerk 00:380 min—
Sat 10 Oct— 01:080 min—
Fri 9 Oct— 01:070 min—