Train Arriva 30873 Zutphen – Winterswijk
It does not run today
Last recorded run: Friday 9 October +5 min
Next service: tomorrow 22:07 from Zutphen · Mon 12 Oct
Next departure 22:07 tomorrow · Zutphen
On-time · 30 days
75%
3/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
75%
3/4 runs under 3 min
RT coverage: 4 full · 0 partial · 2 no data
Typical delay
—
Needs at least 5 runs with data (4 so far)
P90
—
Needs at least 5 runs with data (4 so far)
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
- Fri 9 Oct Max en route +5 min · last fix heading to — +5 min
Distribution · 90 days
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 75% · 3
- 3–10 min 25% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- 100% W n=1
- 100% T n=1
- 0% F n=1
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
| Stop | Sched. |
|---|---|
| 22:07 | |
| 22:14 / 22:15 | |
| 22:21 | |
| 22:29 / 22:30 | |
| 22:37 | |
| 22:40 |
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.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 9 Oct | — 22:47 | +5 min | +5 min |
| Thu 8 Oct | — 22:45 | +2 min | +2 min |
| Wed 7 Oct | — 22:41 | 0 min | — |
| Mon 5 Oct | — 22:42 | 0 min | — |
| Sun 19 Jul | Winterswijk West 22:55 | No data | — |
| Sat 18 Jul | Winterswijk West 22:53 | No data | — |