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