Train NS 7666 Zutphen – Nijmegen
✓ Today’s run finished
Today, last fix heading to Brummen at 18:59 No data
- Zutphen18:07
- Brummen18:12
- Dieren18:17
- Velp18:27
- Arnhem Velperpoort18:33
- Arnhem Centraal18:36
- Nijmegen18:58
Next service: tomorrow 18:07 from Zutphen · Fri 6 Nov
Last 30 days
Arrival delay at Nijmegen, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 7 Oct Max en route +3 min · last fix heading to Zutphen +3 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 17
- 3–10 min 6% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=2
- 67% W n=3
- 100% T n=2
- 100% F n=2
- 100% S n=2
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 18 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 |
|---|---|---|---|
| 18:07 | on time | on time | |
| 18:12 | ≈ on time | ≈ on time | |
| 18:17 / 18:18 | ≈ on time | ≈ on time | |
| 18:23 | ≈ on time | ≈ on time | |
| 18:27 | ≈ on time | ≈ on time | |
| 18:30 | ≈ on time | ≈ on time | |
| 18:33 | ≈ on time | ≈ on time | |
| 18:36 / 18:41 | ≈ on time | ≈ on time | |
| 18:46 | ≈ on time | ≈ on time | |
| 18:50 | ≈ on time | ≈ on time | |
| 18:55 | ≈ on time | ≈ on time | |
| 18:58 | on time | on time |
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 | Brummen 18:59 | No data | — |
| Wed 4 Nov | Brummen 18:59 | No data | — |
| Tue 3 Nov | Brummen 18:59 | No data | — |
| Mon 2 Nov | Zutphen 18:34Partial coverage | 0 min | — |
| Sun 1 Nov | Nijmegen Lent 19:09 | No data | — |
| Sat 31 Oct | Nijmegen Lent 19:10Partial coverage | +2 min | +2 min |
| Fri 30 Oct | Elst 19:04 | No data | — |
| Thu 29 Oct | — 19:01 | 0 min | — |
| Wed 28 Oct | Brummen 19:01 | 0 min | — |
| Tue 27 Oct | — 19:14 | No data | — |
| Mon 26 Oct | Zutphen 19:01 | 0 min | — |
| Sun 25 Oct | Nijmegen Lent 19:10 | No data | — |
| Sat 24 Oct | Nijmegen Lent 19:13 | No data | — |
| Fri 23 Oct | Nijmegen Lent 19:10 | +1 min | — |
| Thu 22 Oct | Arnhem Centraal 19:02 | No data | — |
| Wed 21 Oct | Arnhem Velperpoort 19:02 | 0 min | — |
| Tue 20 Oct | Arnhem Centraal 19:04 | 0 min | — |
| Mon 19 Oct | Arnhem Centraal 18:59Partial coverage | 0 min | — |
| Sun 18 Oct | Nijmegen Lent 19:09 | 0 min | — |
| Sat 17 Oct | Nijmegen Lent 19:09 | No data | — |
| Fri 16 Oct | Nijmegen Lent 19:09 | No data | — |
| Thu 15 Oct | Arnhem Presikhaaf 18:44 | No data | — |
| Wed 14 Oct | Nijmegen Lent 19:09 | No data | — |
| Tue 13 Oct | Arnhem Velperpoort 18:59 | No data | — |
| Mon 12 Oct | Arnhem Centraal 18:59Partial coverage | 0 min | — |
| Sun 11 Oct | Nijmegen Lent 19:09Partial coverage | 0 min | — |
| Sat 10 Oct | Nijmegen Lent 19:11Partial coverage | +2 min | +2 min |
| Fri 9 Oct | Arnhem Velperpoort 19:04Partial coverage | +2 min | +2 min |
| Thu 8 Oct | — 19:00 | 0 min | — |
| Wed 7 Oct | Zutphen 19:06Partial coverage | +3 min | +3 min |