Train NS 7522 Arnhem Centraal – Ede-Wageningen
✓ Today’s run finished
Today, last fix heading to Wolfheze at 07:59 +4 min
- Arnhem Centraal07:34
- Oosterbeek07:38
- Wolfheze07:42
- Ede-Wageningen07:48
Next service: tomorrow 07:34 from Arnhem Centraal · Thu 19 Nov
Last 30 days
Arrival delay at Ede-Wageningen, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 10 Nov Max en route +5 min · last fix heading to Wolfheze +5 min
- Wed 11 Nov Max en route +5 min · last fix heading to Wolfheze +4 min
- Wed 18 Nov Max en route +4 min · last fix heading to Wolfheze +4 min
- Thu 12 Nov Max en route +4 min · last fix heading to Wolfheze +4 min
- Mon 16 Nov Max en route +3 min · last fix heading to Wolfheze +3 min
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 74% · 14
- 3–10 min 26% · 5
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 80% T n=5
- 50% W n=4
- 75% T n=4
- 100% F n=2
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 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 |
|---|---|---|---|
| 07:34 | on time | on time | |
| 07:38 | ≈ on time | ≈ +2 min | |
| 07:42 | ≈ on time | ≈ +3 min | |
| 07:48 | +1 min | +4 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 18 Nov | Wolfheze 07:59Partial coverage | +4 min | +4 min |
| Tue 17 Nov | Wolfheze 07:57 | +1 min | — |
| Mon 16 Nov | Wolfheze 07:59 | +3 min | +3 min |
| Fri 13 Nov | Wolfheze 07:57 | 0 min | — |
| Thu 12 Nov | Wolfheze 07:59 | +4 min | +4 min |
| Wed 11 Nov | Wolfheze 07:59 | +4 min | +5 min |
| Tue 10 Nov | Wolfheze 07:59 | +5 min | +5 min |
| Mon 9 Nov | Wolfheze 07:58 | +2 min | +2 min |
| Fri 6 Nov | Wolfheze 07:58 | No data | — |
| Thu 5 Nov | Wolfheze 07:59 | 0 min | — |
| Wed 4 Nov | Wolfheze 07:54 | 0 min | — |
| Tue 3 Nov | Wolfheze 07:57 | 0 min | — |
| Mon 2 Nov | Wolfheze 07:57 | 0 min | — |
| Mon 19 Oct | Wolfheze 07:57 | 0 min | — |
| Fri 16 Oct | Wolfheze 07:57 | No data | — |
| Thu 15 Oct | Wolfheze 07:57 | 0 min | — |
| Wed 14 Oct | Wolfheze 07:57 | No data | — |
| Tue 13 Oct | Wolfheze 07:57 | 0 min | — |
| Mon 12 Oct | Wolfheze 07:56 | No data | — |
| Fri 9 Oct | Wolfheze 07:57 | +1 min | — |
| Thu 8 Oct | Wolfheze 07:57 | +1 min | +1 min |
| Wed 7 Oct | Wolfheze 07:57 | 0 min | — |
| Tue 6 Oct | Wolfheze 07:57 | +1 min | — |
| Mon 5 Oct | Wolfheze 07:58 | No data | — |
| Fri 2 Oct | Wolfheze 07:57 | No data | — |
| Thu 1 Oct | Wolfheze 07:57 | No data | — |
| Wed 30 Sept | Wolfheze 07:57 | No data | — |
| Tue 29 Sept | Wolfheze 07:57 | No data | — |
| Mon 28 Sept | Wolfheze 07:57 | No data | — |
| Fri 25 Sept | Wolfheze 07:57 | No data | — |