Train NS 5668 Zwolle – Utrecht Centraal
It has not run yet today
Last recorded run: Thursday 5 November No data
Next service: today 18:53 from Zwolle · Fri 6 Nov
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
- Thu 29 Oct Max en route +5 min · last fix heading to — +4 min
- Sat 10 Oct Max en route +4 min · last fix heading to Utrecht Overvecht +4 min
- Wed 7 Oct Max en route +5 min · last fix heading to — +4 min
Distribution · 90 days
22 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 86% · 19
- 3–10 min 14% · 3
- 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
- 75% T n=4
- 100% F n=4
- 67% 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, 22 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 18:53 | on time | on time | |
| 19:00 | ≈ on time | ≈ on time | |
| 19:06 | ≈ on time | ≈ on time | |
| 19:12 | ≈ on time | ≈ +1 min | |
| 19:20 | ≈ on time | ≈ +1 min | |
| 19:24 | ≈ on time | ≈ +1 min | |
| 19:29 | ≈ on time | ≈ +1 min | |
| 19:34 | ≈ on time | ≈ +1 min | |
| 19:39 | ≈ on time | ≈ +1 min | |
| 19:42 | ≈ on time | ≈ +1 min | |
| 19:46 / 19:49 | ≈ on time | ≈ +2 min | |
| 19:56 | ≈ on time | ≈ +2 min | |
| 20:00 | ≈ on time | ≈ +2 min | |
| 20:05 | ≈ on time | ≈ +2 min | |
| 20:09 | on time | +2 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 5 Nov | — 20:09 | No data | — |
| Wed 4 Nov | — 20:13 | +1 min | +1 min |
| Tue 3 Nov | — 20:09 | No data | — |
| Mon 2 Nov | — 20:14 | 0 min | — |
| Sun 1 Nov | Utrecht Overvecht 20:19 | 0 min | — |
| Sat 31 Oct | Utrecht Overvecht 20:22Partial coverage | +3 min | +3 min |
| Fri 30 Oct | Zwolle 20:10Partial coverage | 0 min | — |
| Thu 29 Oct | — 20:19 | +4 min | +5 min |
| Wed 28 Oct | — 20:17 | 0 min | — |
| Tue 27 Oct | — 20:11 | 0 min | — |
| Mon 26 Oct | Amersfoort Centraal 20:15 | No data | — |
| Sun 25 Oct | Utrecht Overvecht 20:19 | No data | — |
| Sat 24 Oct | Utrecht Overvecht 20:19Partial coverage | 0 min | — |
| Fri 23 Oct | Ermelo 20:11Partial coverage | 0 min | +1 min |
| Thu 22 Oct | — 20:13 | 0 min | — |
| Wed 21 Oct | — 20:11 | No data | — |
| Tue 20 Oct | — 20:17 | No data | — |
| Mon 19 Oct | — 20:10 | 0 min | — |
| Sun 18 Oct | Ermelo 19:45 | 0 min | — |
| Sat 17 Oct | Ermelo 19:44 | No data | — |
| Fri 16 Oct | Amersfoort Centraal 20:14 | 0 min | — |
| Thu 15 Oct | — 20:14 | 0 min | — |
| Wed 14 Oct | Amersfoort Schothorst 20:12 | No data | — |
| Tue 13 Oct | — 20:14 | No data | — |
| Mon 12 Oct | — 20:41 | No data | — |
| Sun 11 Oct | Utrecht Overvecht 20:19 | 0 min | — |
| Sat 10 Oct | Utrecht Overvecht 20:23Partial coverage | +4 min | +4 min |
| Fri 9 Oct | — 20:10 | 0 min | — |
| Thu 8 Oct | — 20:11 | 0 min | — |
| Wed 7 Oct | — 20:17 | +4 min | +5 min |