Train NS 7627 Wijchen – Zutphen
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 08:48 from Wijchen · Thu 5 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=3
- 100% T n=3
- 100% W n=4
- 100% T n=1
- 100% F n=1
- 100% S n=4
- 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 |
|---|---|---|---|
| 08:48 | on time | on time | |
| 08:53 | ≈ on time | ≈ on time | |
| 08:56 | ≈ on time | ≈ on time | |
| 09:00 / 09:02 | ≈ on time | ≈ on time | |
| 09:05 | ≈ on time | ≈ on time | |
| 09:10 | ≈ on time | ≈ on time | |
| 09:14 | ≈ on time | ≈ on time | |
| 09:19 / 09:25 | ≈ on time | ≈ on time | |
| 09:27 | ≈ on time | ≈ +1 min | |
| 09:31 | ≈ on time | ≈ +1 min | |
| 09:34 | ≈ on time | ≈ +1 min | |
| 09:38 | ≈ on time | ≈ +1 min | |
| 09:43 / 09:44 | ≈ on time | ≈ +1 min | |
| 09:48 | ≈ on time | ≈ +1 min | |
| 09:54 | on time | +1 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 |
|---|---|---|---|
| Wed 4 Nov | Brummen 10:04Partial coverage | 0 min | — |
| Tue 3 Nov | Brummen 10:04Partial coverage | 0 min | — |
| Mon 2 Nov | Brummen 10:12Partial coverage | 0 min | — |
| Sun 1 Nov | Brummen 10:05 | 0 min | — |
| Sat 31 Oct | Brummen 10:05Partial coverage | 0 min | — |
| Fri 30 Oct | Brummen 10:04 | No data | — |
| Thu 29 Oct | Brummen 10:04 | No data | — |
| Wed 28 Oct | Brummen 10:04Partial coverage | 0 min | — |
| Tue 27 Oct | Brummen 10:04 | No data | — |
| Mon 26 Oct | Brummen 10:04Partial coverage | 0 min | — |
| Sun 25 Oct | Brummen 10:06 | No data | — |
| Sat 24 Oct | Brummen 10:04 | 0 min | — |
| Fri 23 Oct | Brummen 10:05 | No data | — |
| Thu 22 Oct | Brummen 10:05 | No data | — |
| Wed 21 Oct | Brummen 15:34 | 0 min | — |
| Tue 20 Oct | Brummen 10:06 | 0 min | — |
| Mon 19 Oct | Brummen 10:04Partial coverage | 0 min | — |
| Sun 18 Oct | Brummen 10:02 | 0 min | — |
| Sat 17 Oct | Brummen 10:04Partial coverage | +2 min | +2 min |
| Fri 16 Oct | Brummen 10:04 | No data | — |
| Thu 15 Oct | Arnhem Presikhaaf 10:58 | No data | — |
| Wed 14 Oct | Brummen 10:05 | No data | — |
| Tue 13 Oct | Brummen 10:05 | No data | — |
| Mon 12 Oct | Brummen 10:07 | No data | — |
| Sun 11 Oct | Brummen 10:06 | +2 min | +2 min |
| Sat 10 Oct | Brummen 10:05Partial coverage | +1 min | +1 min |
| Fri 9 Oct | Brummen 10:06Partial coverage | +2 min | +2 min |
| Thu 8 Oct | Brummen 10:13Partial coverage | 0 min | +10 min |
| Wed 7 Oct | Brummen 10:06Partial coverage | 0 min | — |
| Tue 6 Oct | Brummen 10:04Partial coverage | 0 min | — |