Train RRReis A 30840 Winterswijk – Zutphen
Running now · updated 13:48
Position estimated from the timetable
Heading to Zutphen 0 min
Estimated arrival at Zutphen 14:23
- Winterswijk13:50
- Winterswijk West13:52
- Lichtenvoorde-Groenlo13:59
- Ruurlo14:08
- Vorden14:14
- Zutphen14:23
Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 19 runs arrived on time.
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 14 Nov Max en route +10 min · last fix heading to Winterswijk +10 min
- Sun 11 Oct Max en route +6 min · last fix heading to Vorden +6 min
- Mon 5 Oct Max en route +5 min · last fix heading to Vorden +5 min
- Fri 9 Oct Max en route +3 min · last fix heading to Vorden +3 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 86% · 24
- 3–10 min 14% · 4
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 100% T n=5
- 100% W n=5
- 100% T n=3
- 67% F n=3
- 80% S n=5
- 67% S n=3
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 | Today |
|---|---|---|---|---|
| 13:50 | on time | on time | ||
| 13:52 | — | — | ||
| 13:59 / 14:00 | — | — | ||
| 14:08 | — | — | ||
| 14:14 / 14:15 | — | — | ||
| 14:23 | — | — |
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 13:45Partial coverage | 0 min | — |
| Thu 19 Nov | Vorden 14:29Partial coverage | +1 min | +1 min |
| Wed 18 Nov | Vorden 14:29Partial coverage | 0 min | — |
| Tue 17 Nov | Vorden 14:29Partial coverage | 0 min | — |
| Mon 16 Nov | Vorden 14:30Partial coverage | +1 min | +1 min |
| Sun 15 Nov | Vorden 14:30Partial coverage | +3 min | +3 min |
| Sat 14 Nov | Winterswijk 14:49 | +10 min | +10 min |
| Fri 13 Nov | Vorden 14:29Partial coverage | +1 min | — |
| Thu 12 Nov | Vorden 14:29Partial coverage | 0 min | — |
| Wed 11 Nov | Vorden 14:29Partial coverage | 0 min | — |
| Tue 10 Nov | Vorden 14:29Partial coverage | +1 min | +1 min |
| Mon 9 Nov | Vorden 14:29Partial coverage | +1 min | +1 min |
| Sun 8 Nov | Vorden 14:30Partial coverage | No data | — |
| Sat 7 Nov | Vorden 14:29Partial coverage | +2 min | +3 min |
| Fri 6 Nov | Vorden 14:29 | No data | — |
| Thu 5 Nov | Vorden 14:29 | No data | — |
| Wed 4 Nov | Vorden 14:29Partial coverage | 0 min | — |
| Tue 3 Nov | Vorden 14:29 | No data | — |
| Mon 2 Nov | Vorden 14:29 | No data | — |
| Sun 1 Nov | Vorden 14:30Partial coverage | 0 min | — |
| Sat 31 Oct | Vorden 14:30Partial coverage | +1 min | +1 min |
| Fri 30 Oct | Vorden 14:29 | No data | — |
| Thu 29 Oct | Vorden 14:29 | No data | — |
| Wed 28 Oct | Vorden 14:29Partial coverage | 0 min | — |
| Tue 27 Oct | Vorden 14:30Partial coverage | 0 min | — |
| Mon 26 Oct | Vorden 14:29 | No data | — |
| Sun 25 Oct | Vorden 14:30 | No data | — |
| Sat 24 Oct | Vorden 14:29Partial coverage | 0 min | — |
| Fri 23 Oct | Vorden 14:37 | No data | — |
| Thu 22 Oct | Vorden 14:29 | No data | — |