Train NS 7663 Wijchen – Zutphen
It has not run yet today
Last recorded run: Thursday 5 November No data
Next service: today 17:48 from Wijchen · Fri 6 Nov
Last 30 days
Arrival delay at Zutphen, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 1 Nov Max en route +27 min · last fix heading to Rheden +27 min
- Fri 23 Oct Max en route +7 min · last fix heading to Brummen +7 min
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 90% · 19
- 3–10 min 5% · 1
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=3
- 100% W n=2
- 100% T n=2
- 50% F n=2
- 100% S n=4
- 67% 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:48 | on time | on time | |
| 17:52 | ≈ on time | ≈ +2 min | |
| 17:55 | ≈ on time | ≈ +3 min | |
| 17:59 / 18:02 | ≈ on time | ≈ +4 min | |
| 18:05 | ≈ on time | ≈ +5 min | |
| 18:10 | ≈ on time | ≈ +7 min | |
| 18:14 | ≈ on time | ≈ +8 min | |
| 18:19 / 18:25 | ≈ on time | ≈ +9 min | |
| 18:27 | ≈ on time | ≈ +11 min | |
| 18:31 | ≈ on time | ≈ +12 min | |
| 18:34 | ≈ on time | ≈ +12 min | |
| 18:38 | ≈ on time | ≈ +13 min | |
| 18:43 / 18:44 | ≈ on time | ≈ +14 min | |
| 18:48 | ≈ on time | ≈ +15 min | |
| 18:54 | on time | +17 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 | Elst 18:54 | No data | — |
| Wed 4 Nov | Arnhem Zuid 18:54Partial coverage | 0 min | — |
| Tue 3 Nov | Elst 18:54Partial coverage | 0 min | — |
| Mon 2 Nov | Elst 18:59Partial coverage | +1 min | +1 min |
| Sun 1 Nov | Rheden 19:49 | +27 min | +27 min |
| Sat 31 Oct | Brummen 19:05Partial coverage | 0 min | — |
| Fri 30 Oct | Brummen 19:02 | No data | — |
| Thu 29 Oct | Nijmegen 18:56Partial coverage | +1 min | +1 min |
| Wed 28 Oct | Elst 18:55Partial coverage | 0 min | — |
| Tue 27 Oct | Nijmegen Lent 18:57 | No data | — |
| Mon 26 Oct | Nijmegen Lent 18:56Partial coverage | 0 min | — |
| Sun 25 Oct | Brummen 19:05 | No data | — |
| Sat 24 Oct | Brummen 19:05 | 0 min | — |
| Fri 23 Oct | Brummen 19:09 | +7 min | +7 min |
| Thu 22 Oct | Dieren 18:58 | No data | — |
| Wed 21 Oct | Rheden 18:56 | No data | — |
| Tue 20 Oct | Dieren 18:55 | 0 min | — |
| Mon 19 Oct | Rheden 18:56Partial coverage | 0 min | — |
| Sun 18 Oct | Brummen 19:04 | 0 min | — |
| Sat 17 Oct | Brummen 19:04Partial coverage | 0 min | — |
| Fri 16 Oct | Brummen 19:02 | No data | — |
| Thu 15 Oct | Arnhem Velperpoort 18:57 | No data | — |
| Wed 14 Oct | Brummen 19:02 | No data | — |
| Tue 13 Oct | Rheden 18:55 | No data | — |
| Mon 12 Oct | Dieren 18:58Partial coverage | 0 min | — |
| Sun 11 Oct | Brummen 19:04 | 0 min | — |
| Sat 10 Oct | Brummen 19:05Partial coverage | 0 min | — |
| Fri 9 Oct | Velp 18:55Partial coverage | 0 min | — |
| Thu 8 Oct | Nijmegen 18:55Partial coverage | 0 min | — |
| Wed 7 Oct | Nijmegen Lent 18:19 | No data | — |