Train NS 7651 Wijchen – Zutphen
✓ Today’s run finished
Today, last fix heading to Brummen at 16:09 +2 min
- Wijchen14:48
- Nijmegen Goffert14:55
- Elst15:10
- Arnhem Centraal15:19
- Arnhem Presikhaaf15:31
- Brummen15:48
- Zutphen15:54
Next service: tomorrow 14:48 from Wijchen · Tue 17 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 12 Nov Max en route +12 min · last fix heading to Brummen +12 min
- Sun 1 Nov Max en route +4 min · last fix heading to Brummen +4 min
- Fri 13 Nov Max en route +3 min · last fix heading to Brummen +3 min
Distribution · 90 days
27 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 24
- 3–10 min 7% · 2
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=3
- 100% W n=4
- 50% T n=2
- 67% F n=3
- 100% S n=5
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 27 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 |
|---|---|---|---|
| 14:48 | on time | on time | |
| 14:52 | ≈ on time | ≈ on time | |
| 14:55 | ≈ on time | ≈ on time | |
| 14:59 / 15:02 | ≈ on time | ≈ on time | |
| 15:05 | ≈ on time | ≈ +1 min | |
| 15:10 | ≈ on time | ≈ +1 min | |
| 15:14 | ≈ on time | ≈ +1 min | |
| 15:19 / 15:25 | ≈ on time | ≈ +1 min | |
| 15:27 | ≈ on time | ≈ +2 min | |
| 15:31 | ≈ on time | ≈ +2 min | |
| 15:34 | ≈ on time | ≈ +2 min | |
| 15:38 | ≈ on time | ≈ +2 min | |
| 15:43 / 15:44 | ≈ on time | ≈ +2 min | |
| 15:48 | ≈ on time | ≈ +3 min | |
| 15:54 | on time | +3 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 |
|---|---|---|---|
| Mon 16 Nov | Brummen 16:09Partial coverage | +2 min | +2 min |
| Sun 15 Nov | Brummen 16:04 | 0 min | — |
| Sat 14 Nov | Brummen 16:04Partial coverage | 0 min | — |
| Fri 13 Nov | Brummen 16:04Partial coverage | +3 min | +3 min |
| Thu 12 Nov | Brummen 16:14Partial coverage | +12 min | +12 min |
| Wed 11 Nov | Brummen 16:04 | +3 min | +3 min |
| Tue 10 Nov | Brummen 16:04Partial coverage | +1 min | +1 min |
| Mon 9 Nov | Brummen 16:04Partial coverage | 0 min | — |
| Sun 8 Nov | Brummen 16:04 | 0 min | — |
| Sat 7 Nov | Brummen 16:04 | No data | — |
| Fri 6 Nov | Brummen 16:04 | No data | — |
| Thu 5 Nov | Brummen 16:05 | No data | — |
| Wed 4 Nov | Brummen 16:04Partial coverage | +2 min | +2 min |
| Tue 3 Nov | Brummen 16:04 | No data | — |
| Mon 2 Nov | Brummen 16:04 | No data | — |
| Sun 1 Nov | Brummen 16:07 | +4 min | +4 min |
| Sat 31 Oct | Brummen 16:04Partial coverage | 0 min | +1 min |
| Fri 30 Oct | Brummen 16:04 | No data | — |
| Thu 29 Oct | Brummen 16:04 | No data | — |
| Wed 28 Oct | Brummen 16:04 | No data | — |
| Tue 27 Oct | Brummen 16:08 | No data | — |
| Mon 26 Oct | Brummen 16:04 | No data | — |
| Sun 25 Oct | Brummen 16:05 | No data | — |
| Sat 24 Oct | Brummen 16:04 | 0 min | — |
| Fri 23 Oct | Brummen 16:10 | 0 min | — |
| Thu 22 Oct | Brummen 16:05 | No data | — |
| Wed 21 Oct | Brummen 16:05 | 0 min | — |
| Tue 20 Oct | Brummen 16:05 | 0 min | — |
| Mon 19 Oct | Brummen 16:05Partial coverage | 0 min | — |
| Sun 18 Oct | Brummen 16:04 | 0 min | — |