Train Arriva 30962 Winterswijk – Arnhem Centraal
It has not run yet today
Last recorded run: Wednesday 4 November +1 min
Next service: today 19:20 from Winterswijk · Thu 5 Nov
Last 30 days
Arrival delay at Arnhem Centraal, 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 +8 min · last fix heading to Arnhem Velperpoort +7 min
- Mon 5 Oct Max en route +6 min · last fix heading to — +6 min
- Fri 23 Oct Max en route +6 min · last fix heading to Winterswijk +6 min
- Sun 18 Oct Max en route +5 min · last fix heading to Arnhem Velperpoort +5 min
- Wed 7 Oct Max en route +4 min · last fix heading to — +4 min
Distribution · 90 days
16 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 63% · 10
- 3–10 min 38% · 6
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 50% M n=2
- 100% T n=4
- 50% W n=2
- 50% T n=2
- 0% F n=1
- 50% S n=2
- 67% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 16 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 |
|---|---|---|---|
| 19:20 | on time | on time | |
| 19:29 / 19:30 | ≈ on time | ≈ +1 min | |
| 19:37 | ≈ on time | ≈ +1 min | |
| 19:44 / 19:45 | ≈ on time | ≈ +1 min | |
| 19:47 | ≈ on time | ≈ +2 min | |
| 19:52 / 19:53 | ≈ on time | ≈ +2 min | |
| 19:56 | ≈ on time | ≈ +2 min | |
| 19:59 / 20:00 | ≈ on time | ≈ +2 min | |
| 20:05 | ≈ +1 min | ≈ +3 min | |
| 20:09 | ≈ +1 min | ≈ +3 min | |
| 20:13 | ≈ +1 min | ≈ +3 min | |
| 20:17 | ≈ +1 min | ≈ +3 min | |
| 20:21 | ≈ +1 min | ≈ +4 min | |
| 20:24 | +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 4 Nov | — 20:29 | +1 min | +2 min |
| Mon 2 Nov | — 20:34 | No data | — |
| Sun 1 Nov | Wehl 20:28 | +1 min | +1 min |
| Sat 31 Oct | Wehl 20:14 | 0 min | — |
| Fri 30 Oct | — 20:28 | No data | — |
| Thu 29 Oct | — 20:27 | +1 min | — |
| Wed 28 Oct | — 20:29 | No data | — |
| Tue 27 Oct | — 20:30 | 0 min | — |
| Mon 26 Oct | Gaanderen 20:28 | No data | — |
| Sun 25 Oct | Arnhem Velperpoort 20:45 | No data | — |
| Sat 24 Oct | Arnhem Velperpoort 20:42 | No data | — |
| Fri 23 Oct | Winterswijk 20:33Partial coverage | +6 min | +6 min |
| Thu 22 Oct | — 20:29 | No data | — |
| Wed 21 Oct | — 20:28 | No data | — |
| Tue 20 Oct | — 20:34 | 0 min | — |
| Sun 18 Oct | Arnhem Velperpoort 20:40Partial coverage | +5 min | +5 min |
| Sat 17 Oct | Arnhem Velperpoort 20:38 | No data | — |
| Fri 16 Oct | Doetinchem 20:28 | No data | — |
| Wed 14 Oct | Gaanderen 20:01 | No data | — |
| Tue 13 Oct | — 20:30 | 0 min | — |
| Mon 12 Oct | — 20:28 | 0 min | — |
| Sun 11 Oct | Arnhem Velperpoort 20:37Partial coverage | +2 min | +2 min |
| Sat 10 Oct | Arnhem Velperpoort 20:43Partial coverage | +7 min | +8 min |
| Fri 9 Oct | — 19:17 | No data | — |
| Thu 8 Oct | — 20:29 | +4 min | +4 min |
| Wed 7 Oct | — 20:29 | +4 min | +4 min |
| Tue 6 Oct | — 20:26 | +1 min | — |
| Mon 5 Oct | — 20:33 | +6 min | +6 min |
| Sun 4 Oct | Arnhem Velperpoort 20:36 | No data | — |
| Sat 3 Oct | Arnhem Velperpoort 20:43 | No data | — |