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