Train RRReis A 30941 Arnhem Centraal – Winterswijk
✓ Today’s run finished
Today, last fix heading to Aalten at 14:44 No data
- Arnhem Centraal13:36
- Westervoort13:42
- Zevenaar13:50
- Doetinchem De Huet14:04
- Gaanderen14:12
- Aalten14:29
- Winterswijk14:40
Next service: tomorrow 13:36 from Arnhem Centraal · Fri 6 Nov
Last 30 days
Arrival delay at Winterswijk, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sat 10 Oct Max en route +9 min · last fix heading to Aalten +8 min
- Wed 4 Nov Max en route +4 min · last fix heading to Aalten +4 min
- Fri 9 Oct Max en route +3 min · last fix heading to Aalten +3 min
Distribution · 90 days
14 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 79% · 11
- 3–10 min 21% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=3
- 67% W n=3
- 100% T n=2
- 0% F n=1
- 50% S n=2
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 14 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 |
|---|---|---|---|
| 13:36 | on time | on time | |
| 13:38 | — | — | |
| 13:42 | — | — | |
| 13:46 | — | — | |
| 13:50 | — | — | |
| 13:55 | — | — | |
| 13:59 / 14:00 | — | — | |
| 14:04 | — | — | |
| 14:07 / 14:08 | — | — | |
| 14:12 | — | — | |
| 14:14 / 14:15 | — | — | |
| 14:21 | — | — | |
| 14:29 / 14:30 | — | — | |
| 14:40 | — | — |
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 | Aalten 14:44 | No data | — |
| Wed 4 Nov | Aalten 14:47Partial coverage | +4 min | +4 min |
| Tue 3 Nov | Aalten 14:44 | No data | — |
| Mon 2 Nov | Aalten 14:44 | No data | — |
| Sun 1 Nov | Aalten 14:44 | No data | — |
| Sat 31 Oct | Aalten 14:44 | No data | — |
| Fri 30 Oct | Aalten 14:44 | No data | — |
| Thu 29 Oct | Aalten 14:47Partial coverage | 0 min | — |
| Wed 28 Oct | Aalten 14:44Partial coverage | 0 min | — |
| Tue 27 Oct | Aalten 14:44Partial coverage | 0 min | — |
| Mon 26 Oct | Aalten 14:44 | No data | — |
| Sun 25 Oct | Aalten 14:46 | No data | — |
| Sat 24 Oct | Aalten 14:44Partial coverage | 0 min | — |
| Fri 23 Oct | Aalten 14:46 | No data | — |
| Thu 22 Oct | Aalten 14:44 | No data | — |
| Wed 21 Oct | Aalten 14:44 | No data | — |
| Tue 20 Oct | Aalten 14:44Partial coverage | 0 min | — |
| Mon 19 Oct | Aalten 14:45 | No data | — |
| Sun 18 Oct | Aalten 14:45Partial coverage | 0 min | — |
| Sat 17 Oct | Aalten 14:44 | No data | — |
| Fri 16 Oct | Aalten 14:44 | No data | — |
| Thu 15 Oct | Aalten 14:44 | No data | — |
| Wed 14 Oct | Aalten 14:44 | No data | — |
| Tue 13 Oct | Aalten 14:44 | No data | — |
| Mon 12 Oct | Aalten 14:44 | No data | — |
| Sun 11 Oct | Aalten 14:44Partial coverage | 0 min | — |
| Sat 10 Oct | Aalten 14:52Partial coverage | +8 min | +9 min |
| Fri 9 Oct | Aalten 14:47Partial coverage | +3 min | +3 min |
| Thu 8 Oct | Aalten 14:45Partial coverage | +1 min | +1 min |
| Wed 7 Oct | Aalten 14:45Partial coverage | +1 min | +1 min |