Train NS 5639 Utrecht Centraal – Zwolle

Utrecht Centraal 11:51 → Zwolle 13:06 Daily 1 h 15 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 11:51 from Utrecht Centraal · Fri 6 Nov

Next departure 11:51 today · Utrecht Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 7 full · 11 partial · 11 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 8 full · 13 partial · 65 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 21
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=2
  • 100% T n=2
  • 100% F n=3
  • 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, 21 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
11:51on time on time
11:55≈ on time ≈ on time
12:00≈ on time ≈ on time
12:03≈ on time ≈ on time
12:10 / 12:12≈ on time ≈ on time
12:16≈ on time ≈ on time
12:19≈ on time ≈ on time
12:24≈ on time ≈ on time
12:29≈ on time ≈ on time
12:34≈ on time ≈ on time
12:38≈ on time ≈ on time
12:46≈ on time ≈ on time
12:52≈ on time ≈ on time
12:59≈ on time ≈ on time
13: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 5 NovWezep 13:19No data—
Wed 4 NovWezep 13:14Partial coverage0 min—
Tue 3 NovWezep 13:140 min—
Mon 2 NovWezep 13:14Partial coverage0 min—
Sun 1 NovWezep 13:150 min—
Sat 31 OctWezep 13:18Partial coverage0 min+2 min
Fri 30 OctWezep 13:14No data—
Thu 29 OctWezep 13:14Partial coverage0 min—
Wed 28 OctWezep 13:14No data—
Tue 27 OctWezep 13:140 min—
Mon 26 OctWezep 13:20Partial coverage0 min—
Sun 25 OctWezep 13:14No data—
Sat 24 OctWezep 13:14Partial coverage0 min—
Fri 23 OctWezep 13:140 min—
Thu 22 OctWezep 13:14No data—
Wed 21 OctWezep 13:14No data—
Tue 20 OctWezep 13:130 min—
Mon 19 OctWezep 13:14Partial coverage0 min—
Sun 18 OctWezep 13:140 min—
Sat 17 OctWezep 13:13No data—
Fri 16 OctWezep 13:130 min—
Thu 15 OctWezep 13:12No data—
Wed 14 OctWezep 13:13No data—
Tue 13 OctWezep 13:12No data—
Mon 12 OctWezep 13:12No data—
Sun 11 OctWezep 13:14Partial coverage0 min—
Sat 10 OctWezep 13:14Partial coverage0 min+3 min
Fri 9 OctWezep 13:14Partial coverage0 min—
Thu 8 OctWezep 13:14Partial coverage0 min—
Wed 7 OctWezep 13:21Partial coverage0 min—