Train NS 7659 Nijmegen – Zutphen
✓ Today’s run finished
Today, last fix heading to Brummen at 18:04 0 min
- Nijmegen17:03
- Elst17:11
- Arnhem Centraal17:20
- Arnhem Presikhaaf17:31
- Velp17:34
- Brummen17:48
- Zutphen17:54
Next service: tomorrow 17:03 from Nijmegen · Mon 16 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
- Sat 10 Oct Max en route +10 min · last fix heading to Brummen +10 min
- Wed 11 Nov Max en route +5 min · last fix heading to Brummen +5 min
- Sun 8 Nov Max en route +4 min · last fix heading to Brummen +4 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
- 75% W n=4
- 100% T n=2
- 100% F n=3
- 80% S n=5
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 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 |
|---|---|---|---|
| 17:03 | on time | on time | |
| 17:06 | ≈ on time | ≈ on time | |
| 17:11 | ≈ on time | ≈ on time | |
| 17:15 | ≈ on time | ≈ +1 min | |
| 17:20 / 17:25 | ≈ on time | ≈ +1 min | |
| 17:27 | ≈ on time | ≈ +1 min | |
| 17:31 | ≈ on time | ≈ +1 min | |
| 17:34 | ≈ on time | ≈ +2 min | |
| 17:38 | ≈ on time | ≈ +2 min | |
| 17:43 / 17:44 | ≈ on time | ≈ +2 min | |
| 17:48 | ≈ on time | ≈ +2 min | |
| 17: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 |
|---|---|---|---|
| Sun 15 Nov | Brummen 18:04Partial coverage | 0 min | — |
| Sat 14 Nov | Brummen 18:04 | 0 min | — |
| Fri 13 Nov | Brummen 18:02 | +3 min | +3 min |
| Thu 12 Nov | Brummen 18:02 | 0 min | — |
| Wed 11 Nov | Brummen 18:04 | +5 min | +5 min |
| Tue 10 Nov | Brummen 18:02 | +2 min | +2 min |
| Mon 9 Nov | Brummen 18:02 | +2 min | +2 min |
| Sun 8 Nov | Brummen 18:07Partial coverage | +4 min | +4 min |
| Sat 7 Nov | Brummen 18:04 | 0 min | — |
| Fri 6 Nov | Brummen 18:02 | 0 min | — |
| Thu 5 Nov | Brummen 18:02 | No data | — |
| Wed 4 Nov | Brummen 18:02 | No data | — |
| Tue 3 Nov | Brummen 18:02 | No data | — |
| Mon 2 Nov | Brummen 18:02 | No data | — |
| Sun 1 Nov | Brummen 18:05Partial coverage | +1 min | — |
| Sat 31 Oct | Brummen 18:05 | 0 min | — |
| Fri 30 Oct | Brummen 18:02 | No data | — |
| Thu 29 Oct | Brummen 18:02 | No data | — |
| Wed 28 Oct | Brummen 18:02 | 0 min | — |
| Tue 27 Oct | Brummen 18:02 | No data | — |
| Mon 26 Oct | Brummen 18:02 | 0 min | — |
| Sun 25 Oct | Brummen 18:11 | No data | — |
| Sat 24 Oct | Brummen 18:04 | 0 min | — |
| Fri 23 Oct | Brummen 18:05 | No data | — |
| Thu 22 Oct | Brummen 18:02 | No data | — |
| Wed 21 Oct | Brummen 18:04 | 0 min | — |
| Tue 20 Oct | Brummen 18:02 | 0 min | — |
| Mon 19 Oct | Brummen 18:02 | 0 min | — |
| Sun 18 Oct | Brummen 18:05Partial coverage | 0 min | — |
| Sat 17 Oct | Brummen 18:04 | No data | — |