Train NS 5617 Utrecht Centraal – Zwolle
✓ Today’s run finished
Today, last fix heading to Wezep at 07:47 0 min
- Utrecht Centraal06:21
- Bilthoven06:30
- Amersfoort Schothorst06:46
- Nijkerk06:54
- Ermelo07:04
- Wezep07:29
- Zwolle07:36
Next service: tomorrow 06:21 from Utrecht Centraal · Fri 6 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 9 Oct Max en route +4 min · last fix heading to Wezep +4 min
Distribution · 90 days
24 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 96% · 23
- 3–10 min 4% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=5
- 100% W n=5
- 100% T n=5
- 75% F n=4
- 100% S n=1
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 24 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 |
|---|---|---|---|
| 06:21 | on time | on time | |
| 06:25 | ≈ on time | ≈ on time | |
| 06:30 | ≈ on time | ≈ on time | |
| 06:33 | ≈ on time | ≈ on time | |
| 06:40 / 06:42 | ≈ on time | ≈ on time | |
| 06:46 | ≈ on time | ≈ on time | |
| 06:49 | ≈ on time | ≈ on time | |
| 06:54 | ≈ on time | ≈ +1 min | |
| 06:59 | ≈ on time | ≈ +1 min | |
| 07:04 | ≈ on time | ≈ +1 min | |
| 07:08 | ≈ on time | ≈ +1 min | |
| 07:16 | ≈ on time | ≈ +1 min | |
| 07:22 | ≈ on time | ≈ +1 min | |
| 07:29 | ≈ on time | ≈ +1 min | |
| 07: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 |
|---|---|---|---|
| Thu 5 Nov | Wezep 07:47Partial coverage | 0 min | — |
| Wed 4 Nov | Wezep 07:44Partial coverage | +1 min | +1 min |
| Tue 3 Nov | Wezep 07:44Partial coverage | 0 min | — |
| Mon 2 Nov | Wezep 07:49Partial coverage | 0 min | — |
| Fri 30 Oct | Wezep 07:45Partial coverage | +1 min | +1 min |
| Thu 29 Oct | Wezep 07:44Partial coverage | +1 min | +1 min |
| Wed 28 Oct | Wezep 07:55 | 0 min | — |
| Tue 27 Oct | Wezep 07:44Partial coverage | 0 min | — |
| Mon 26 Oct | Wezep 07:44Partial coverage | 0 min | — |
| Fri 23 Oct | Wezep 07:44Partial coverage | 0 min | — |
| Thu 22 Oct | Wezep 07:50Partial coverage | 0 min | — |
| Wed 21 Oct | Wezep 07:44Partial coverage | 0 min | — |
| Tue 20 Oct | Wezep 07:44Partial coverage | 0 min | — |
| Mon 19 Oct | Wezep 07:44Partial coverage | 0 min | — |
| Sat 17 Oct | Wezep 07:44 | 0 min | — |
| Fri 16 Oct | Wezep 07:43 | 0 min | — |
| Thu 15 Oct | Wezep 07:43 | 0 min | — |
| Wed 14 Oct | Wezep 07:51 | +3 min | +3 min |
| Tue 13 Oct | Wezep 07:43 | 0 min | — |
| Mon 12 Oct | Wezep 07:43 | 0 min | — |
| Fri 9 Oct | Wezep 07:47Partial coverage | +4 min | +4 min |
| Thu 8 Oct | Wezep 07:46Partial coverage | +2 min | +2 min |
| Wed 7 Oct | Wezep 07:44Partial coverage | 0 min | — |
| Tue 6 Oct | Wezep 07:45Partial coverage | 0 min | — |
| Mon 5 Oct | Wezep 07:46 | No data | — |
| Fri 2 Oct | Wezep 07:44 | No data | — |
| Thu 1 Oct | Wezep 07:46 | No data | — |
| Wed 30 Sept | Wezep 07:44 | No data | — |
| Tue 29 Sept | Wezep 07:44 | No data | — |
| Mon 28 Sept | Wezep 07:44 | No data | — |