Train RRReis A 30822 Winterswijk – Zutphen
✓ Today’s run finished
Today, last fix heading to Vorden at 10:13 No data
- Winterswijk09:20
- Winterswijk West09:22
- Lichtenvoorde-Groenlo09:29
- Ruurlo09:38
- Vorden09:44
- Zutphen09:53
Next service: tomorrow 09:20 from Winterswijk · Fri 6 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
- Tue 6 Oct Max en route +5 min · last fix heading to Vorden +4 min
Distribution · 90 days
9 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 8
- 3–10 min 11% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 67% T n=3
- 100% W n=3
- 100% T n=1
- 100% F n=1
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 9 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 |
|---|---|---|---|
| 09:20 | on time | on time | |
| 09:22 | — | — | |
| 09:29 / 09:30 | — | — | |
| 09:38 | — | — | |
| 09:44 / 09:45 | — | — | |
| 09:53 | — | — |
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 | Vorden 10:13 | No data | — |
| Wed 4 Nov | Vorden 09:59Partial coverage | 0 min | — |
| Tue 3 Nov | Vorden 09:59 | No data | — |
| Mon 2 Nov | Vorden 09:59 | No data | — |
| Fri 30 Oct | Vorden 10:00 | No data | — |
| Thu 29 Oct | Vorden 10:01 | No data | — |
| Wed 28 Oct | Vorden 10:00Partial coverage | 0 min | — |
| Tue 27 Oct | Vorden 10:00Partial coverage | 0 min | — |
| Mon 26 Oct | Vorden 09:59 | No data | — |
| Fri 23 Oct | Vorden 10:02 | No data | — |
| Thu 22 Oct | Vorden 10:02 | No data | — |
| Wed 21 Oct | Vorden 10:10 | No data | — |
| Tue 20 Oct | Vorden 10:02Partial coverage | 0 min | — |
| Mon 19 Oct | Vorden 09:59Partial coverage | 0 min | — |
| Fri 16 Oct | Vorden 09:59 | No data | — |
| Thu 15 Oct | Vorden 10:00 | No data | — |
| Wed 14 Oct | Vorden 09:59 | No data | — |
| Tue 13 Oct | Vorden 10:00 | No data | — |
| Mon 12 Oct | Vorden 10:00 | No data | — |
| Fri 9 Oct | Vorden 10:01Partial coverage | 0 min | — |
| Thu 8 Oct | Vorden 09:59Partial coverage | 0 min | — |
| Wed 7 Oct | Vorden 09:59Partial coverage | 0 min | — |
| Tue 6 Oct | Vorden 10:03Partial coverage | +4 min | +5 min |
| Mon 5 Oct | Vorden 10:01 | No data | — |
| Fri 2 Oct | Vorden 10:00 | No data | — |
| Thu 1 Oct | Vorden 10:02 | No data | — |
| Wed 30 Sept | Vorden 10:03 | No data | — |
| Tue 29 Sept | Vorden 10:03 | No data | — |
| Mon 28 Sept | Vorden 09:59 | No data | — |
| Fri 25 Sept | Vorden 09:59 | No data | — |