Train RRReis A 30860 Winterswijk → Zutphen
RRReis A 30860 Winterswijk–Zutphen: final delay under 3 min on 12 of its 19 runs with data in the last 30 days (63%). Median final delay: +2 min. TrainsRadar data as of 22 Nov 2026, 16:34 (GMT+1).
An alert on this phone or computer when the 30860 is 5 min or more late, every day it runs. No account, no email.
It has not run yet today
Last recorded run: Saturday 21 November +16 min
Next service: today 18:50 from Winterswijk · Sun 22 Nov
Last 30 days
Arrival delay at Zutphen, 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 21 Nov Max en route +16 min · last fix heading to Vorden +16 min
- Thu 8 Oct Max en route +9 min · last fix heading to — +9 min
- Sun 15 Nov Max en route +7 min · last fix heading to Vorden +7 min
- Sun 1 Nov Max en route +5 min · last fix heading to Vorden +5 min
- Fri 20 Nov Max en route +5 min · last fix heading to Vorden +5 min
Distribution · 90 days
28 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 71% · 20
- 3–10 min 25% · 7
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=3
- 100% W n=3
- 25% T n=4
- 33% F n=3
- 80% S n=5
- 60% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 28 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 |
|---|---|---|---|
| 18:50 | on time | on time | |
| 18:52 | ≈ on time | ≈ on time | |
| 18:59 / 19:00 | ≈ on time | ≈ +2 min | |
| 19:08 | ≈ on time | ≈ +3 min | |
| 19:14 / 19:15 | ≈ on time | ≈ +3 min | |
| 19:23 | on time | +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 |
|---|---|---|---|
| Sat 21 Nov | Vorden 19:44Partial coverage | +16 min | +16 min |
| Fri 20 Nov | Vorden 19:32Partial coverage | +5 min | +5 min |
| Thu 19 Nov | — 19:29 | +4 min | +4 min |
| Tue 17 Nov | — 19:28 | +1 min | +1 min |
| Mon 16 Nov | — 19:27 | +1 min | +1 min |
| Sun 15 Nov | Vorden 19:34Partial coverage | +7 min | +7 min |
| Sat 14 Nov | Vorden 19:29Partial coverage | +2 min | +2 min |
| Fri 13 Nov | Winterswijk West 19:29Partial coverage | +3 min | +3 min |
| Thu 12 Nov | — 19:29 | +4 min | +4 min |
| Wed 11 Nov | — 19:28 | +3 min | +3 min |
| Mon 9 Nov | — 19:24 | 0 min | — |
| Sun 8 Nov | Vorden 19:29Partial coverage | +2 min | +2 min |
| Sat 7 Nov | Vorden 19:29Partial coverage | +1 min | +1 min |
| Thu 5 Nov | — 19:27 | No data | — |
| Wed 4 Nov | — 19:24 | 0 min | — |
| Mon 2 Nov | — 19:24 | 0 min | — |
| Sun 1 Nov | Vorden 19:34Partial coverage | +5 min | +5 min |
| Sat 31 Oct | Vorden 19:29Partial coverage | 0 min | — |
| Fri 30 Oct | Winterswijk West 19:26 | No data | — |
| Thu 29 Oct | — 19:26 | 0 min | — |
| Wed 28 Oct | — 19:26 | No data | — |
| Tue 27 Oct | — 19:30 | 0 min | — |
| Mon 26 Oct | — 19:27 | No data | — |
| Sun 25 Oct | Vorden 19:29 | No data | — |
| Sat 24 Oct | Vorden 19:32 | No data | — |
| Fri 23 Oct | Vorden 19:30Partial coverage | +1 min | +1 min |
| Thu 22 Oct | — 19:26 | No data | — |
| Wed 21 Oct | — 19:27 | No data | — |
| Tue 20 Oct | — 19:26 | 0 min | — |
| Mon 19 Oct | — 19:26 | No data | — |