Train NS 7658 Zutphen – Wijchen
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 16:07 from Zutphen · Thu 5 Nov
Last 30 days
Arrival delay at Wijchen, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 12 Oct Max en route +11 min · last fix heading to Nijmegen Dukenburg +11 min
- Fri 9 Oct Max en route +6 min · last fix heading to Nijmegen Dukenburg +6 min
Distribution · 90 days
20 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 90% · 18
- 3–10 min 5% · 1
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 50% M n=2
- 100% T n=3
- 100% W n=4
- 100% T n=1
- 67% F n=3
- 100% 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, 20 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:07 | on time | on time | |
| 16:12 | ≈ on time | ≈ on time | |
| 16:17 / 16:18 | ≈ on time | ≈ on time | |
| 16:23 | ≈ on time | ≈ on time | |
| 16:27 | ≈ on time | ≈ on time | |
| 16:30 | ≈ on time | ≈ on time | |
| 16:33 | ≈ on time | ≈ +1 min | |
| 16:36 / 16:41 | ≈ on time | ≈ +1 min | |
| 16:46 | ≈ on time | ≈ +1 min | |
| 16:50 | ≈ on time | ≈ +1 min | |
| 16:55 | ≈ on time | ≈ +1 min | |
| 16:59 / 17:00 | ≈ on time | ≈ +1 min | |
| 17:04 | ≈ on time | ≈ +1 min | |
| 17:07 | ≈ on time | ≈ +1 min | |
| 17:11 | 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 | Nijmegen Dukenburg 17:19Partial coverage | 0 min | — |
| Tue 3 Nov | Nijmegen Dukenburg 17:19 | 0 min | — |
| Mon 2 Nov | Nijmegen Dukenburg 17:19 | No data | — |
| Sun 1 Nov | Nijmegen Lent 17:09 | 0 min | — |
| Sat 31 Oct | Nijmegen Dukenburg 17:21 | 0 min | — |
| Fri 30 Oct | Nijmegen Dukenburg 17:22 | 0 min | — |
| Thu 29 Oct | Nijmegen Dukenburg 17:21 | No data | — |
| Wed 28 Oct | Nijmegen Dukenburg 17:21 | 0 min | — |
| Tue 27 Oct | Nijmegen Dukenburg 17:21 | No data | — |
| Mon 26 Oct | Nijmegen Dukenburg 17:21 | No data | — |
| Sun 25 Oct | Nijmegen Lent 17:09 | No data | — |
| Sat 24 Oct | Nijmegen Dukenburg 17:21 | 0 min | — |
| Fri 23 Oct | Nijmegen Dukenburg 17:25 | 0 min | — |
| Thu 22 Oct | Nijmegen Dukenburg 17:22 | No data | — |
| Wed 21 Oct | Nijmegen Dukenburg 17:24 | 0 min | — |
| Tue 20 Oct | Nijmegen Dukenburg 17:21 | 0 min | — |
| Mon 19 Oct | Nijmegen Dukenburg 17:21 | No data | — |
| Sun 18 Oct | Nijmegen Lent 17:09 | 0 min | — |
| Sat 17 Oct | Nijmegen Dukenburg 17:24 | 0 min | — |
| Fri 16 Oct | Nijmegen Dukenburg 17:21 | No data | — |
| Thu 15 Oct | Nijmegen Dukenburg 17:17 | No data | — |
| Wed 14 Oct | Nijmegen Dukenburg 17:21 | No data | — |
| Tue 13 Oct | Nijmegen Dukenburg 17:21 | No data | — |
| Mon 12 Oct | Nijmegen Dukenburg 17:44 | +11 min | +11 min |
| Sun 11 Oct | Nijmegen Lent 17:09 | 0 min | — |
| Sat 10 Oct | Nijmegen Dukenburg 17:21 | 0 min | — |
| Fri 9 Oct | Nijmegen Dukenburg 17:26 | +6 min | +6 min |
| Thu 8 Oct | Nijmegen Goffert 17:25 | 0 min | — |
| Wed 7 Oct | Nijmegen Dukenburg 17:21 | 0 min | — |
| Tue 6 Oct | Nijmegen Dukenburg 17:21 | 0 min | — |