Train RRReis A 30704 Doetinchem – Arnhem Centraal
It does not run today
Last recorded run: Friday 6 November No data
Next service: Monday 05:38 from Doetinchem · Mon 9 Nov
Last 30 days
Arrival delay at Arnhem Centraal, 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 15 Oct Max en route +9 min · last fix heading to Arnhem Velperpoort +9 min
- Tue 20 Oct Max en route +3 min · last fix heading to Arnhem Velperpoort +3 min
Distribution · 90 days
15 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 87% · 13
- 3–10 min 13% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 75% T n=4
- 100% W n=3
- 75% T n=4
- 100% F n=1
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 15 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 |
|---|---|---|---|
| 05:38 | on time | on time | |
| 05:41 | ≈ on time | ≈ on time | |
| 05:44 / 05:45 | ≈ on time | ≈ on time | |
| 05:50 | ≈ on time | ≈ +1 min | |
| 05:54 / 05:55 | ≈ on time | ≈ +1 min | |
| 05:59 | ≈ on time | ≈ +1 min | |
| 06:03 | ≈ on time | ≈ +2 min | |
| 06:07 | ≈ on time | ≈ +2 min | |
| 06:10 | on time | +2 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 6 Nov | Arnhem Velperpoort 06:22 | No data | — |
| Tue 3 Nov | Arnhem Velperpoort 06:19Partial coverage | 0 min | — |
| Mon 2 Nov | Arnhem Velperpoort 06:34Partial coverage | 0 min | — |
| Thu 29 Oct | Arnhem Velperpoort 06:22Partial coverage | +1 min | +1 min |
| Wed 28 Oct | Arnhem Velperpoort 06:22Partial coverage | 0 min | — |
| Mon 26 Oct | Arnhem Velperpoort 06:23Partial coverage | +1 min | +1 min |
| Fri 23 Oct | Arnhem Velperpoort 06:22 | +1 min | +1 min |
| Thu 22 Oct | Arnhem Velperpoort 06:21 | 0 min | — |
| Wed 21 Oct | Arnhem Velperpoort 06:21 | 0 min | — |
| Tue 20 Oct | Arnhem Velperpoort 06:24 | +3 min | +3 min |
| Mon 19 Oct | Arnhem Velperpoort 06:21 | 0 min | — |
| Thu 15 Oct | Arnhem Velperpoort 06:34Partial coverage | +9 min | +9 min |
| Wed 14 Oct | Arnhem Velperpoort 06:21Partial coverage | No data | — |
| Tue 13 Oct | Arnhem Velperpoort 06:22Partial coverage | 0 min | — |
| Thu 8 Oct | Arnhem Velperpoort 06:22Partial coverage | 0 min | — |
| Wed 7 Oct | Arnhem Velperpoort 06:22Partial coverage | +1 min | +1 min |
| Tue 6 Oct | Arnhem Velperpoort 06:21Partial coverage | 0 min | — |
| Mon 5 Oct | Arnhem Velperpoort 06:23 | No data | — |
| Fri 2 Oct | Arnhem Velperpoort 06:22 | No data | — |
| Thu 1 Oct | Arnhem Velperpoort 06:25 | No data | — |
| Wed 30 Sept | Arnhem Velperpoort 06:26 | No data | — |
| Tue 29 Sept | Arnhem Velperpoort 06:22 | No data | — |
| Mon 28 Sept | Arnhem Velperpoort 06:25 | No data | — |
| Fri 25 Sept | Arnhem Velperpoort 06:22 | No data | — |
| Thu 24 Sept | Arnhem Velperpoort 06:22 | No data | — |
| Wed 23 Sept | Arnhem Velperpoort 06:21 | No data | — |
| Tue 22 Sept | Arnhem Velperpoort 06:21 | No data | — |
| Mon 21 Sept | Arnhem Velperpoort 06:27 | No data | — |
| Fri 18 Sept | Arnhem Velperpoort 06:22 | No data | — |
| Thu 17 Sept | Arnhem Velperpoort 06:21 | No data | — |