Train RRReis A 30722 Doetinchem – Arnhem Centraal
It has not run yet today
Last recorded run: Thursday 5 November No data
Next service: today 10:08 from Doetinchem · Fri 6 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
- Wed 4 Nov Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min
Distribution · 90 days
14 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 13
- 3–10 min 7% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=4
- 67% W n=3
- 100% T n=2
- 100% F n=1
- 100% S n=1
- 100% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 14 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 |
|---|---|---|---|
| 10:08 | on time | +1 min | |
| 10:11 | — | — | |
| 10:14 / 10:15 | — | — | |
| 10:20 | — | — | |
| 10:24 / 10:25 | — | — | |
| 10:29 | — | — | |
| 10:33 | — | — | |
| 10:37 | — | — | |
| 10: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.
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 | Arnhem Velperpoort 10:49 | No data | — |
| Wed 4 Nov | Arnhem Velperpoort 10:54Partial coverage | +4 min | +4 min |
| Tue 3 Nov | Arnhem Velperpoort 10:53Partial coverage | 0 min | — |
| Mon 2 Nov | Arnhem Velperpoort 10:54Partial coverage | 0 min | — |
| Sun 1 Nov | Arnhem Velperpoort 10:37 | 0 min | — |
| Sat 31 Oct | Arnhem Velperpoort 10:37 | +1 min | — |
| Fri 30 Oct | Arnhem Velperpoort 10:52 | No data | — |
| Thu 29 Oct | Arnhem Velperpoort 10:51Partial coverage | 0 min | — |
| Wed 28 Oct | Arnhem Velperpoort 10:52Partial coverage | 0 min | — |
| Tue 27 Oct | Arnhem Velperpoort 10:52Partial coverage | 0 min | — |
| Mon 26 Oct | Arnhem Velperpoort 10:52 | No data | — |
| Fri 23 Oct | Arnhem Velperpoort 10:57 | No data | — |
| Thu 22 Oct | Arnhem Velperpoort 10:57 | No data | — |
| Wed 21 Oct | Arnhem Velperpoort 10:51 | No data | — |
| Tue 20 Oct | Arnhem Velperpoort 10:51Partial coverage | 0 min | — |
| Mon 19 Oct | Arnhem Velperpoort 10:52Partial coverage | 0 min | — |
| Fri 16 Oct | Arnhem Velperpoort 10:52 | No data | — |
| Thu 15 Oct | Arnhem Velperpoort 10:52 | No data | — |
| Wed 14 Oct | Arnhem Velperpoort 10:51 | No data | — |
| Tue 13 Oct | Arnhem Velperpoort 10:52 | No data | — |
| Mon 12 Oct | Arnhem Velperpoort 10:52 | No data | — |
| Fri 9 Oct | Arnhem Velperpoort 10:54Partial coverage | +2 min | +2 min |
| Thu 8 Oct | Arnhem Velperpoort 10:52Partial coverage | +1 min | — |
| Wed 7 Oct | Zevenaar 12:02 | 0 min | — |
| Tue 6 Oct | Arnhem Velperpoort 10:51Partial coverage | 0 min | — |
| Mon 5 Oct | Arnhem Velperpoort 10:57 | No data | — |
| Fri 2 Oct | Arnhem Velperpoort 10:52 | No data | — |
| Thu 1 Oct | Arnhem Velperpoort 10:51 | No data | — |
| Wed 30 Sept | Arnhem Velperpoort 10:54 | No data | — |
| Tue 29 Sept | Arnhem Velperpoort 10:51 | No data | — |