Train RRReis A 30438 Winterswijk – Apeldoorn
It does not run today
Last recorded run: Sunday 15 November +1 min
Next service: Saturday 13:20 from Winterswijk · Sat 21 Nov
Last 30 days
Arrival delay at Apeldoorn, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 1 Nov Max en route +14 min · last fix heading to Zutphen +14 min
- Sun 11 Oct Max en route +8 min · last fix heading to Apeldoorn De Maten +8 min
- Sat 14 Nov Max en route +7 min · last fix heading to Zutphen +7 min
- Sun 8 Nov Max en route +5 min · last fix heading to Zutphen +5 min
Distribution · 90 days
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 60% · 6
- 3–10 min 30% · 3
- 10–30 min 10% · 1
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 80% S n=5
- 40% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 10 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:20 | on time | on time | |
| 13:22 | ≈ on time | ≈ on time | |
| 13:29 / 13:30 | ≈ on time | ≈ +1 min | |
| 13:38 | ≈ on time | ≈ +2 min | |
| 13:44 / 13:45 | ≈ on time | ≈ +2 min | |
| 13:53 / 13:55 | ≈ on time | ≈ +3 min | |
| 14:08 | on time | +5 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 |
|---|---|---|---|
| Sun 15 Nov | Zutphen 14:10Partial coverage | +1 min | +3 min |
| Sat 14 Nov | Zutphen 14:14 | +7 min | +7 min |
| Sun 8 Nov | Zutphen 14:14Partial coverage | +5 min | +5 min |
| Sat 7 Nov | Zutphen 14:09 | 0 min | — |
| Sun 1 Nov | Zutphen 14:25Partial coverage | +14 min | +14 min |
| Sat 31 Oct | Zutphen 14:12 | 0 min | — |
| Sun 25 Oct | Zutphen 14:11 | No data | — |
| Sat 24 Oct | Zutphen 14:11 | 0 min | — |
| Sun 18 Oct | Zutphen 14:11Partial coverage | 0 min | — |
| Sat 17 Oct | Zutphen 14:11 | No data | — |
| Sun 11 Oct | Apeldoorn De Maten 14:27Partial coverage | +8 min | +8 min |
| Sat 10 Oct | Zutphen 14:10 | +1 min | — |
| Sun 4 Oct | Zutphen 14:09 | No data | — |
| Sat 3 Oct | Zutphen 14:10 | No data | — |
| Sun 27 Sept | Zutphen 14:09 | No data | — |
| Sat 26 Sept | Zutphen 14:09 | No data | — |
| Sun 20 Sept | Zutphen 14:10 | No data | — |
| Sat 19 Sept | Zutphen 14:10 | No data | — |
| Sun 6 Sept | Zutphen 14:09 | No data | — |
| Sat 5 Sept | Zutphen 14:12 | No data | — |
| Sun 30 Aug | Zutphen 14:09 | No data | — |
| Sat 29 Aug | Zutphen 14:10 | No data | — |
| Sun 23 Aug | Zutphen 14:09 | No data | — |
| Sat 22 Aug | Zutphen 14:16 | No data | — |