Train RRReis A 30927 Arnhem Centraal – Winterswijk
✓ Today’s run finished
Today, last fix heading to Aalten at 11:14 No data
- Arnhem Centraal10:05
- Westervoort10:11
- Zevenaar10:19
- Doetinchem De Huet10:33
- Gaanderen10:42
- Aalten10:59
- Winterswijk11:10
Next service: tomorrow 10:05 from Arnhem Centraal · Sun 8 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
Distribution · 90 days
15 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 15
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=3
- 100% W n=2
- 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 (14 stops).
Last 90 days, 15 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 |
|---|---|---|---|
| 10:05 | on time | on time | |
| 10:07 | ≈ on time | ≈ on time | |
| 10:11 | ≈ on time | ≈ on time | |
| 10:15 | ≈ on time | ≈ on time | |
| 10:19 / 10:20 | ≈ on time | ≈ on time | |
| 10:24 | ≈ on time | ≈ on time | |
| 10:29 / 10:30 | ≈ on time | ≈ on time | |
| 10:33 | ≈ on time | ≈ on time | |
| 10:37 / 10:38 | ≈ on time | ≈ on time | |
| 10:42 | ≈ on time | ≈ on time | |
| 10:44 / 10:45 | ≈ on time | ≈ on time | |
| 10:51 | ≈ on time | ≈ on time | |
| 10:59 / 11:00 | ≈ on time | ≈ on time | |
| 11:10 | 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 |
|---|---|---|---|
| Sat 7 Nov | Aalten 11:14 | No data | — |
| Fri 6 Nov | Aalten 11:14 | No data | — |
| Thu 5 Nov | Aalten 11:14 | No data | — |
| Wed 4 Nov | Aalten 11:14Partial coverage | +1 min | +1 min |
| Tue 3 Nov | Aalten 11:14 | No data | — |
| Mon 2 Nov | Aalten 11:14 | No data | — |
| Sun 1 Nov | Aalten 11:15 | 0 min | — |
| Sat 31 Oct | Aalten 11:15 | +1 min | +1 min |
| Fri 30 Oct | Aalten 11:14 | No data | — |
| Thu 29 Oct | Aalten 11:14 | No data | — |
| Wed 28 Oct | Aalten 11:14Partial coverage | 0 min | — |
| Tue 27 Oct | Aalten 11:14Partial coverage | 0 min | — |
| Mon 26 Oct | Aalten 11:14 | No data | — |
| Sun 25 Oct | Aalten 11:14 | No data | — |
| Sat 24 Oct | Aalten 11:14 | 0 min | — |
| Fri 23 Oct | Aalten 11:17 | No data | — |
| Thu 22 Oct | Aalten 11:14 | No data | — |
| Wed 21 Oct | Aalten 11:16 | No data | — |
| Tue 20 Oct | Aalten 11:14 | 0 min | — |
| Mon 19 Oct | Aalten 11:14 | 0 min | — |
| Sun 18 Oct | Aalten 11:14 | 0 min | — |
| Sat 17 Oct | Aalten 11:17 | 0 min | — |
| Fri 16 Oct | Aalten 11:15 | No data | — |
| Thu 15 Oct | Aalten 11:14 | No data | — |
| Wed 14 Oct | Aalten 11:15 | No data | — |
| Tue 13 Oct | Aalten 11:14 | No data | — |
| Mon 12 Oct | Aalten 11:14 | No data | — |
| Sun 11 Oct | Aalten 11:14 | 0 min | — |
| Sat 10 Oct | Aalten 11:14 | 0 min | — |
| Fri 9 Oct | Aalten 11:14Partial coverage | 0 min | — |