Train NS 7669 Nijmegen – Zutphen
✓ Today’s run finished
Today, last fix heading to — at 20:24 +2 min
- Nijmegen19:33
- Elst19:41
- Arnhem Centraal19:50
- Arnhem Presikhaaf20:01
- Velp20:04
- Dieren20:13
- Zutphen20:24
Next service: tomorrow 19:33 from Nijmegen · Sat 14 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 8 Nov Max en route +13 min · last fix heading to Arnhem Zuid +13 min
- Tue 6 Oct Max en route +12 min · last fix heading to — +12 min
- Wed 4 Nov Max en route +11 min · last fix heading to — +11 min
- Sat 31 Oct Max en route +6 min · last fix heading to Brummen +6 min
- Sun 18 Oct Max en route +4 min · last fix heading to Arnhem Zuid +4 min
Distribution · 90 days
24 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 71% · 17
- 3–10 min 17% · 4
- 10–30 min 13% · 3
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 33% T n=3
- 50% W n=2
- 100% T n=3
- 100% F n=4
- 33% S n=3
- 50% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 24 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 |
|---|---|---|---|
| 19:33 | on time | on time | |
| 19:36 | ≈ on time | ≈ +1 min | |
| 19:41 | ≈ on time | ≈ +2 min | |
| 19:45 | ≈ on time | ≈ +3 min | |
| 19:50 / 19:55 | ≈ on time | ≈ +4 min | |
| 19:57 | ≈ +1 min | ≈ +5 min | |
| 20:01 | ≈ +1 min | ≈ +6 min | |
| 20:04 | ≈ +1 min | ≈ +7 min | |
| 20:08 | ≈ +1 min | ≈ +8 min | |
| 20:13 / 20:14 | ≈ +1 min | ≈ +9 min | |
| 20:18 | ≈ +1 min | ≈ +10 min | |
| 20:24 | +1 min | +11 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 |
|---|---|---|---|
| Fri 13 Nov | — 20:24 | +2 min | +2 min |
| Thu 12 Nov | — 20:24 | +2 min | +2 min |
| Wed 11 Nov | — 20:24 | 0 min | — |
| Tue 10 Nov | — 20:34 | +4 min | +4 min |
| Mon 9 Nov | — 20:24 | 0 min | — |
| Sun 8 Nov | Arnhem Zuid 20:13 | +13 min | +13 min |
| Sat 7 Nov | Brummen 20:34Partial coverage | 0 min | — |
| Fri 6 Nov | — 20:27 | +1 min | +2 min |
| Thu 5 Nov | — 20:25 | No data | — |
| Wed 4 Nov | — 20:34 | +11 min | +11 min |
| Tue 3 Nov | — 20:24 | 0 min | — |
| Mon 2 Nov | — 20:39 | No data | — |
| Sun 1 Nov | Arnhem Zuid 19:59 | +1 min | +1 min |
| Sat 31 Oct | Brummen 20:41Partial coverage | +6 min | +6 min |
| Thu 29 Oct | — 20:25 | 0 min | — |
| Wed 28 Oct | — 20:25 | No data | — |
| Tue 27 Oct | — 20:26 | No data | — |
| Mon 26 Oct | Arnhem Zuid 20:26Partial coverage | 0 min | — |
| Sun 25 Oct | Arnhem Zuid 20:02 | No data | — |
| Sat 24 Oct | Brummen 20:38 | No data | — |
| Fri 23 Oct | — 20:28 | 0 min | +28 min |
| Thu 22 Oct | — 20:26 | No data | — |
| Wed 21 Oct | — 20:25 | No data | — |
| Tue 20 Oct | — 20:08 | No data | — |
| Mon 19 Oct | — 19:52 | 0 min | — |
| Sun 18 Oct | Arnhem Zuid 20:04 | +4 min | +4 min |
| Sat 17 Oct | Brummen 20:36 | No data | — |
| Fri 16 Oct | Arnhem Centraal 20:27 | No data | — |
| Wed 14 Oct | Arnhem Zuid 20:25 | No data | — |
| Tue 13 Oct | — 20:35 | No data | — |