Train RRReis A 17845 Apeldoorn – Zutphen
It does not run today
Last recorded run: Friday 6 November No data
Next service: tomorrow 14:36 from Apeldoorn · Mon 9 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
Distribution · 90 days
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 10
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% 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 (5 stops).
Last 90 days, 10 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 |
|---|---|---|---|
| 14:36 | on time | +1 min | |
| 14:39 | — | — | |
| 14:44 / 14:45 | — | — | |
| 14:50 | — | — | |
| 14:55 | — | — |
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 6 Nov | Voorst-Empe 15:04 | No data | — |
| Thu 5 Nov | Voorst-Empe 15:04 | No data | — |
| Wed 4 Nov | Voorst-Empe 15:04Partial coverage | +1 min | +1 min |
| Tue 3 Nov | Voorst-Empe 15:04 | No data | — |
| Mon 2 Nov | Voorst-Empe 15:04 | No data | — |
| Fri 30 Oct | Voorst-Empe 15:04 | No data | — |
| Thu 29 Oct | Voorst-Empe 15:04 | No data | — |
| Wed 28 Oct | Voorst-Empe 15:04Partial coverage | 0 min | — |
| Tue 27 Oct | Voorst-Empe 15:05Partial coverage | 0 min | — |
| Mon 26 Oct | Voorst-Empe 15:04 | No data | — |
| Fri 23 Oct | Voorst-Empe 15:04 | No data | — |
| Thu 22 Oct | Voorst-Empe 15:04 | No data | — |
| Wed 21 Oct | Voorst-Empe 15:04 | No data | — |
| Tue 20 Oct | Voorst-Empe 15:05Partial coverage | 0 min | — |
| Mon 19 Oct | Voorst-Empe 15:04Partial coverage | 0 min | — |
| Fri 16 Oct | Voorst-Empe 15:04 | No data | — |
| Thu 15 Oct | Voorst-Empe 15:04 | No data | — |
| Wed 14 Oct | Voorst-Empe 15:05 | No data | — |
| Tue 13 Oct | Voorst-Empe 15:04 | No data | — |
| Mon 12 Oct | Voorst-Empe 15:04 | No data | — |
| Fri 9 Oct | Voorst-Empe 15:04Partial coverage | 0 min | — |
| Thu 8 Oct | Voorst-Empe 15:05Partial coverage | +1 min | — |
| Wed 7 Oct | Voorst-Empe 15:04Partial coverage | 0 min | — |
| Tue 6 Oct | Voorst-Empe 15:04Partial coverage | 0 min | +1 min |
| Mon 5 Oct | Voorst-Empe 15:04Partial coverage | 0 min | — |
| Fri 2 Oct | Voorst-Empe 15:05 | No data | — |
| Thu 1 Oct | Voorst-Empe 15:04 | No data | — |
| Wed 30 Sept | Voorst-Empe 15:04 | No data | — |
| Tue 29 Sept | Voorst-Empe 15:04 | No data | — |
| Mon 28 Sept | Voorst-Empe 15:05 | No data | — |