Train NS 5657 Utrecht Centraal – Zwolle
It has not run yet today
Last recorded run: Wednesday 4 November No data
Next service: today 16: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
Worst days
- Tue 6 Oct Max en route +13 min · last fix heading to Wezep +13 min
- Sat 31 Oct Max en route +5 min · last fix heading to Wezep +4 min
Distribution · 90 days
15 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 87% · 13
- 3–10 min 7% · 1
- 10–30 min 7% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 0% T n=1
- 100% W n=1
- 100% T n=1
- 100% F n=2
- 75% 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, 15 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 |
|---|---|---|---|
| 16:21 | on time | on time | |
| 16:25 | ≈ on time | ≈ on time | |
| 16:30 | ≈ on time | ≈ on time | |
| 16:33 | ≈ on time | ≈ on time | |
| 16:40 / 16:42 | ≈ on time | ≈ on time | |
| 16:46 | ≈ on time | ≈ on time | |
| 16:50 | ≈ on time | ≈ on time | |
| 16:54 | ≈ on time | ≈ +1 min | |
| 17:00 | ≈ on time | ≈ +1 min | |
| 17:04 | ≈ on time | ≈ +1 min | |
| 17:09 | ≈ on time | ≈ +1 min | |
| 17:16 | ≈ on time | ≈ +1 min | |
| 17:23 | ≈ on time | ≈ +1 min | |
| 17:29 | ≈ on time | ≈ +1 min | |
| 17: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 | Wezep 17:48 | No data | — |
| Tue 3 Nov | Wezep 17:43 | No data | — |
| Mon 2 Nov | Wezep 17:39Partial coverage | 0 min | — |
| Sun 1 Nov | Wezep 17:44 | 0 min | — |
| Sat 31 Oct | Wezep 17:48 | +4 min | +5 min |
| Fri 30 Oct | Wezep 17:43 | No data | — |
| Thu 29 Oct | Wezep 17:38 | No data | — |
| Wed 28 Oct | Wezep 17:43 | No data | — |
| Tue 27 Oct | Wezep 17:44 | No data | — |
| Mon 26 Oct | Wezep 17:43 | No data | — |
| Sun 25 Oct | Wezep 17:46 | No data | — |
| Sat 24 Oct | Wezep 17:43 | 0 min | — |
| Fri 23 Oct | Wezep 17:44Partial coverage | 0 min | — |
| Thu 22 Oct | Wezep 17:43 | No data | — |
| Wed 21 Oct | Wezep 17:43 | No data | — |
| Tue 20 Oct | Wezep 17:43 | No data | — |
| Mon 19 Oct | Wezep 17:43 | No data | — |
| Sun 18 Oct | Wezep 17:43 | 0 min | — |
| Sat 17 Oct | Wezep 17:44 | 0 min | — |
| Fri 16 Oct | Wezep 17:42 | No data | — |
| Thu 15 Oct | Wezep 17:42 | No data | — |
| Wed 14 Oct | Wezep 17:45 | No data | — |
| Tue 13 Oct | Wezep 17:43 | No data | — |
| Mon 12 Oct | Wezep 17:43 | 0 min | — |
| Sun 11 Oct | Wezep 17:44 | 0 min | — |
| Sat 10 Oct | Wezep 17:44 | 0 min | — |
| Fri 9 Oct | Wezep 17:43Partial coverage | 0 min | — |
| Thu 8 Oct | Wezep 17:43Partial coverage | +3 min | +3 min |
| Wed 7 Oct | Wezep 17:43Partial coverage | +1 min | +2 min |
| Tue 6 Oct | Wezep 18:04Partial coverage | +13 min | +13 min |