Train NS 7653 Wijchen – Zutphen
It has not run yet today
Last recorded run: Saturday 14 November 0 min
Next service: today 15:18 from Wijchen · Sun 15 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
- Thu 8 Oct Max en route +4 min · last fix heading to Brummen +4 min
- Fri 13 Nov Max en route +4 min · last fix heading to Brummen +4 min
Distribution · 90 days
28 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 26
- 3–10 min 7% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=3
- 100% W n=5
- 67% T n=3
- 67% F n=3
- 100% S n=6
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 28 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 |
|---|---|---|---|
| 15:18 | on time | on time | |
| 15:22 | ≈ on time | ≈ on time | |
| 15:25 | ≈ on time | ≈ on time | |
| 15:29 / 15:32 | ≈ on time | ≈ on time | |
| 15:35 | ≈ on time | ≈ on time | |
| 15:40 | ≈ on time | ≈ on time | |
| 15:44 | ≈ on time | ≈ on time | |
| 15:49 / 15:55 | ≈ on time | ≈ +1 min | |
| 15:57 | ≈ on time | ≈ +1 min | |
| 16:01 | ≈ on time | ≈ +1 min | |
| 16:04 | ≈ on time | ≈ +1 min | |
| 16:08 | ≈ on time | ≈ +1 min | |
| 16:13 / 16:14 | ≈ on time | ≈ +1 min | |
| 16:18 | ≈ on time | ≈ +1 min | |
| 16:24 | 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 |
|---|---|---|---|
| Sat 14 Nov | Brummen 16:34Partial coverage | 0 min | — |
| Fri 13 Nov | Brummen 16:37Partial coverage | +4 min | +4 min |
| Thu 12 Nov | Brummen 16:34Partial coverage | +2 min | +2 min |
| Wed 11 Nov | Brummen 16:34 | 0 min | — |
| Tue 10 Nov | Brummen 16:34Partial coverage | +2 min | +2 min |
| Mon 9 Nov | Brummen 16:34Partial coverage | +3 min | +3 min |
| Sun 8 Nov | Arnhem Zuid 15:59 | 0 min | — |
| Sat 7 Nov | Brummen 16:34Partial coverage | 0 min | — |
| Fri 6 Nov | Brummen 16:34 | No data | — |
| Thu 5 Nov | Brummen 16:34 | No data | — |
| Wed 4 Nov | Brummen 16:37Partial coverage | +2 min | +3 min |
| Tue 3 Nov | Brummen 16:34Partial coverage | 0 min | — |
| Mon 2 Nov | Brummen 16:37 | No data | — |
| Sun 1 Nov | Arnhem Zuid 16:03 | +2 min | +2 min |
| Sat 31 Oct | Brummen 16:34Partial coverage | 0 min | — |
| Fri 30 Oct | Brummen 16:34Partial coverage | 0 min | — |
| Thu 29 Oct | Brummen 16:36Partial coverage | 0 min | — |
| Wed 28 Oct | Brummen 16:35Partial coverage | 0 min | — |
| Tue 27 Oct | Brummen 16:38 | No data | — |
| Mon 26 Oct | Brummen 16:34 | No data | — |
| Sun 25 Oct | Arnhem Zuid 16:01 | No data | — |
| Sat 24 Oct | Brummen 16:34 | 0 min | — |
| Fri 23 Oct | Brummen 16:34 | No data | — |
| Thu 22 Oct | Brummen 16:34 | No data | — |
| Wed 21 Oct | Brummen 16:36 | No data | — |
| Tue 20 Oct | Brummen 16:34 | No data | — |
| Mon 19 Oct | Brummen 16:36Partial coverage | 0 min | — |
| Sun 18 Oct | Arnhem Zuid 16:00 | 0 min | — |
| Sat 17 Oct | Brummen 16:36Partial coverage | 0 min | — |
| Fri 16 Oct | Brummen 16:35 | No data | — |