Train NS 5661 Utrecht Centraal – Zwolle
✓ Today’s run finished
Today, last fix heading to Harderwijk at 18:39 0 min
- Utrecht Centraal17:21
- Bilthoven17:30
- Amersfoort Schothorst17:46
- Nijkerk17:54
- Harderwijk18:09
- Nunspeet18:16
- Zwolle18:36
Next service: tomorrow 17:21 from Utrecht Centraal · Thu 5 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
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=2
- 100% W n=4
- 100% T n=1
- 100% F n=4
- 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 17:21 | on time | on time | |
| 17:25 | ≈ on time | ≈ on time | |
| 17:30 | ≈ on time | ≈ on time | |
| 17:33 | ≈ on time | ≈ on time | |
| 17:40 / 17:42 | ≈ on time | ≈ on time | |
| 17:46 | ≈ on time | ≈ on time | |
| 17:50 | ≈ on time | ≈ +1 min | |
| 17:54 | ≈ on time | ≈ +1 min | |
| 18:00 | ≈ on time | ≈ +1 min | |
| 18:04 | ≈ on time | ≈ +1 min | |
| 18:09 | ≈ on time | ≈ +1 min | |
| 18:16 | ≈ on time | ≈ +1 min | |
| 18:23 | ≈ on time | ≈ +1 min | |
| 18:29 | ≈ on time | ≈ +1 min | |
| 18:36 | on time | +1 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 |
|---|---|---|---|
| Wed 4 Nov | Harderwijk 18:39Partial coverage | 0 min | — |
| Tue 3 Nov | Harderwijk 18:37 | No data | — |
| Mon 2 Nov | Harderwijk 18:37Partial coverage | +3 min | +3 min |
| Sun 1 Nov | Wezep 18:44 | +1 min | +2 min |
| Sat 31 Oct | Wezep 18:44 | 0 min | — |
| Fri 30 Oct | Wezep 18:43Partial coverage | 0 min | — |
| Thu 29 Oct | Putten 18:37 | No data | — |
| Wed 28 Oct | Harderwijk 18:37Partial coverage | 0 min | — |
| Tue 27 Oct | Ermelo 18:38 | No data | — |
| Mon 26 Oct | Harderwijk 18:50Partial coverage | 0 min | — |
| Sun 25 Oct | Wezep 18:44 | No data | — |
| Sat 24 Oct | Wezep 18:44 | 0 min | — |
| Fri 23 Oct | Wezep 18:43Partial coverage | 0 min | — |
| Thu 22 Oct | Wezep 18:43 | No data | — |
| Wed 21 Oct | Wezep 18:43 | No data | — |
| Tue 20 Oct | Wezep 18:43Partial coverage | 0 min | — |
| Mon 19 Oct | Wezep 18:43 | No data | — |
| Sun 18 Oct | Wezep 18:43 | 0 min | — |
| Sat 17 Oct | Wezep 18:43 | No data | — |
| Fri 16 Oct | Wezep 18:41 | 0 min | — |
| Thu 15 Oct | Wezep 18:41 | No data | — |
| Wed 14 Oct | Wezep 18:42 | 0 min | — |
| Tue 13 Oct | Wezep 18:46 | No data | — |
| Mon 12 Oct | Wezep 18:41 | 0 min | — |
| Sun 11 Oct | Wezep 18:43 | 0 min | — |
| Sat 10 Oct | Wezep 18:46 | +2 min | +3 min |
| Fri 9 Oct | Wezep 18:43Partial coverage | 0 min | — |
| Thu 8 Oct | Putten 18:39Partial coverage | +2 min | +2 min |
| Wed 7 Oct | Harderwijk 18:37Partial coverage | 0 min | — |
| Tue 6 Oct | Ermelo 18:40Partial coverage | +1 min | +2 min |