Train NS 5669 Utrecht Centraal – Zwolle
It has not run yet today
Last recorded run: Friday 6 November +3 min
Next service: today 19:20 from Utrecht Centraal · Sat 7 Nov
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
- Fri 23 Oct Max en route +8 min · last fix heading to Utrecht Overvecht +7 min
- Sun 11 Oct Max en route +13 min · last fix heading to Wezep +5 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 91% · 21
- 3–10 min 9% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=3
- 100% W n=4
- 100% T n=2
- 75% F n=4
- 100% S n=3
- 67% S n=3
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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 19:20 | on time | on time | |
| 19:24 | ≈ on time | ≈ on time | |
| 19:31 | ≈ on time | ≈ +1 min | |
| 19:34 | ≈ on time | ≈ +1 min | |
| 19:40 / 19:42 | ≈ on time | ≈ +1 min | |
| 19:46 | ≈ on time | ≈ +1 min | |
| 19:49 | ≈ on time | ≈ +1 min | |
| 19:54 | ≈ on time | ≈ +1 min | |
| 19:59 | ≈ on time | ≈ +1 min | |
| 20:04 | ≈ on time | ≈ +2 min | |
| 20:08 | ≈ on time | ≈ +2 min | |
| 20:16 | ≈ on time | ≈ +2 min | |
| 20:22 | ≈ on time | ≈ +2 min | |
| 20:29 | ≈ on time | ≈ +2 min | |
| 20:36 | on time | +3 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 |
|---|---|---|---|
| Fri 6 Nov | — 20:43 | +3 min | +3 min |
| Thu 5 Nov | — 20:38 | 0 min | — |
| Wed 4 Nov | — 20:39 | +1 min | +2 min |
| Mon 2 Nov | — 20:44 | 0 min | — |
| Sun 1 Nov | Wezep 20:43 | 0 min | — |
| Sat 31 Oct | Wezep 20:44 | 0 min | — |
| Fri 30 Oct | — 20:45 | 0 min | — |
| Wed 28 Oct | — 20:37 | 0 min | — |
| Tue 27 Oct | — 20:40 | No data | — |
| Mon 26 Oct | Amersfoort Vathorst 20:37 | No data | — |
| Sun 25 Oct | Wezep 20:44 | No data | — |
| Sat 24 Oct | Wezep 20:44 | 0 min | — |
| Fri 23 Oct | Utrecht Overvecht 20:50 | +7 min | +8 min |
| Thu 22 Oct | — 20:38 | No data | — |
| Wed 21 Oct | — 20:57 | 0 min | — |
| Tue 20 Oct | — 20:44 | 0 min | — |
| Mon 19 Oct | — 20:37 | 0 min | — |
| Sun 18 Oct | Wezep 20:45 | +1 min | +2 min |
| Sat 17 Oct | Wezep 20:43 | No data | — |
| Fri 16 Oct | Nijkerk 20:36 | No data | — |
| Thu 15 Oct | — 20:39 | No data | — |
| Wed 14 Oct | Amersfoort Vathorst 20:36 | No data | — |
| Tue 13 Oct | — 20:37 | 0 min | — |
| Mon 12 Oct | — 20:45 | 0 min | — |
| Sun 11 Oct | Wezep 20:49 | +5 min | +13 min |
| Sat 10 Oct | Wezep 20:44 | 0 min | — |
| Fri 9 Oct | — 20:38 | +2 min | +2 min |
| Thu 8 Oct | — 20:50 | 0 min | — |
| Wed 7 Oct | — 20:38 | 0 min | — |
| Tue 6 Oct | — 20:37 | 0 min | — |