Train Arriva 30475 Apeldoorn – Winterswijk
✓ Today’s run finished
Today, last fix heading to — at 23:09 No data
- Apeldoorn22:23
- Zutphen22:36
- Vorden22:44
- Ruurlo22:51
- Lichtenvoorde-Groenlo22:59
- Winterswijk West23:07
- Winterswijk23:10
Next service: tomorrow 22:23 from Apeldoorn · 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
- Fri 23 Oct Max en route +10 min · last fix heading to — +9 min
- Mon 12 Oct Max en route +7 min · last fix heading to — +5 min
- Thu 8 Oct Max en route +4 min · last fix heading to — +4 min
- Sun 1 Nov Max en route +4 min · last fix heading to Winterswijk West +4 min
- Sun 18 Oct Max en route +4 min · last fix heading to Winterswijk West +3 min
Distribution · 90 days
12 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 58% · 7
- 3–10 min 42% · 5
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 50% M n=2
- 100% T n=2
- 100% W n=3
- 0% T n=1
- 0% F n=1
- — S n=0
- 33% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 12 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 |
|---|---|---|---|
| 22:23 | on time | on time | |
| 22:36 / 22:37 | ≈ on time | ≈ +2 min | |
| 22:44 / 22:45 | ≈ on time | ≈ +3 min | |
| 22:51 | ≈ on time | ≈ +4 min | |
| 22:59 / 23:00 | ≈ on time | ≈ +5 min | |
| 23:07 | ≈ on time | ≈ +6 min | |
| 23:10 | on time | +6 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 |
|---|---|---|---|
| Thu 5 Nov | — 23:09 | No data | — |
| Wed 4 Nov | — 23:12 | 0 min | — |
| Sun 1 Nov | Winterswijk West 23:24Partial coverage | +4 min | +4 min |
| Sat 31 Oct | Winterswijk West 23:21 | No data | — |
| Fri 30 Oct | — 23:16 | No data | — |
| Wed 28 Oct | — 23:13 | No data | — |
| Tue 27 Oct | — 23:13 | 0 min | — |
| Mon 26 Oct | — 23:14 | No data | — |
| Sun 25 Oct | Winterswijk West 23:21 | No data | — |
| Sat 24 Oct | Zutphen 23:14 | No data | — |
| Fri 23 Oct | — 23:22 | +9 min | +10 min |
| Tue 20 Oct | — 23:16 | No data | — |
| Mon 19 Oct | — 23:12 | No data | — |
| Sun 18 Oct | Winterswijk West 23:25Partial coverage | +3 min | +4 min |
| Sat 17 Oct | Winterswijk West 23:22 | No data | — |
| Thu 15 Oct | — 23:21 | No data | — |
| Wed 14 Oct | — 23:12 | 0 min | — |
| Tue 13 Oct | — 23:12 | No data | — |
| Mon 12 Oct | — 23:18 | +5 min | +7 min |
| Sun 11 Oct | Winterswijk West 23:21Partial coverage | 0 min | — |
| Thu 8 Oct | — 23:18 | +4 min | +4 min |
| Wed 7 Oct | — 23:13 | 0 min | — |
| Tue 6 Oct | — 23:11 | 0 min | — |
| Mon 5 Oct | — 23:13 | 0 min | — |
| Sun 4 Oct | Winterswijk West 23:21 | No data | — |
| Sat 3 Oct | Winterswijk West 23:23 | No data | — |
| Sun 27 Sept | Winterswijk West 23:21 | No data | — |
| Sat 26 Sept | Winterswijk West 23:21 | No data | — |
| Sun 20 Sept | Winterswijk West 23:21 | No data | — |
| Sat 19 Sept | Lichtenvoorde-Groenlo 23:08 | No data | — |