Train RRReis A 30734 Doetinchem – Arnhem Centraal
✓ Today’s run finished
Today, last fix heading to Arnhem Velperpoort at 13:53 No data
- Doetinchem13:08
- Doetinchem De Huet13:11
- Didam13:20
- Zevenaar13:24
- Duiven13:30
- Arnhem Velperpoort13:39
- Arnhem Centraal13:41
Next service: tomorrow 13:08 from Doetinchem · Sat 7 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
- Sun 1 Nov Max en route +3 min · last fix heading to Arnhem Velperpoort +3 min
Distribution · 90 days
11 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 10
- 3–10 min 9% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=2
- 100% W n=3
- 100% T n=1
- 100% F n=1
- 100% S n=1
- 0% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 11 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 |
|---|---|---|---|
| 13:08 | on time | on time | |
| 13:11 | ≈ on time | ≈ +2 min | |
| 13:14 / 13:15 | ≈ on time | ≈ +2 min | |
| 13:20 | ≈ on time | ≈ +2 min | |
| 13:24 / 13:26 | ≈ on time | ≈ +2 min | |
| 13:30 | ≈ on time | ≈ +2 min | |
| 13:34 | ≈ on time | ≈ +2 min | |
| 13:39 | ≈ on time | ≈ +2 min | |
| 13:41 | 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 13:53 | No data | — |
| Thu 5 Nov | Arnhem Velperpoort 13:53 | No data | — |
| Wed 4 Nov | Arnhem Velperpoort 13:53Partial coverage | 0 min | — |
| Tue 3 Nov | Arnhem Velperpoort 13:53 | No data | — |
| Mon 2 Nov | Arnhem Velperpoort 13:53 | No data | — |
| Sun 1 Nov | Arnhem Velperpoort 13:47 | +3 min | +3 min |
| Sat 31 Oct | Arnhem Velperpoort 13:46 | +1 min | +1 min |
| Fri 30 Oct | Arnhem Velperpoort 13:54 | No data | — |
| Thu 29 Oct | Arnhem Velperpoort 13:52 | No data | — |
| Wed 28 Oct | Arnhem Velperpoort 13:52 | 0 min | — |
| Tue 27 Oct | Arnhem Velperpoort 13:53 | 0 min | — |
| Mon 26 Oct | Arnhem Velperpoort 13:52 | No data | — |
| Fri 23 Oct | Arnhem Velperpoort 13:53 | No data | — |
| Thu 22 Oct | Arnhem Velperpoort 13:52 | No data | — |
| Wed 21 Oct | Arnhem Velperpoort 13:52 | No data | — |
| Tue 20 Oct | Arnhem Velperpoort 13:52 | 0 min | — |
| Mon 19 Oct | Arnhem Velperpoort 13:53Partial coverage | 0 min | — |
| Fri 16 Oct | Arnhem Velperpoort 13:53 | No data | — |
| Thu 15 Oct | Arnhem Velperpoort 13:53 | No data | — |
| Wed 14 Oct | Arnhem Velperpoort 13:53 | No data | — |
| Tue 13 Oct | Arnhem Velperpoort 13:53 | No data | — |
| Mon 12 Oct | Arnhem Velperpoort 13:53 | No data | — |
| Fri 9 Oct | Arnhem Velperpoort 13:53Partial coverage | 0 min | — |
| Thu 8 Oct | Arnhem Velperpoort 13:54Partial coverage | +1 min | +2 min |
| Wed 7 Oct | Arnhem Velperpoort 13:53Partial coverage | 0 min | — |
| Tue 6 Oct | Arnhem Velperpoort 13:53 | No data | — |
| Mon 5 Oct | Arnhem Velperpoort 13:53Partial coverage | 0 min | — |
| Fri 2 Oct | Arnhem Velperpoort 13:53 | No data | — |
| Thu 1 Oct | Arnhem Velperpoort 13:53 | No data | — |
| Wed 30 Sept | Arnhem Velperpoort 13:53 | No data | — |