Train RRReis A 30726 Doetinchem – Arnhem Centraal

Doetinchem 11:08 → Arnhem Centraal 11:41 Daily 0 h 33 min · 9 stops RRReis A

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 11:08 from Doetinchem · Thu 5 Nov

Next departure 11:08 today · Doetinchem
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 5 full · 6 partial · 11 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 5 full · 6 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

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

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 100% · 11
  • 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=2
  • 100% T n=2
  • 100% F n=1
  • 100% S n=1
  • — S n=0

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.

StopSched.Usually 9 days in 10
11:08on time on time
11:11≈ on time ≈ on time
11:14 / 11:15≈ on time ≈ on time
11:20≈ on time ≈ on time
11:24 / 11:26≈ on time ≈ on time
11:30≈ on time ≈ on time
11:34≈ on time ≈ on time
11:39≈ on time ≈ on time
11:41on time on time

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

DateLast stopFinalMax
Wed 4 NovArnhem Velperpoort 11:53Partial coverage0 min—
Tue 3 NovArnhem Velperpoort 11:53Partial coverage0 min—
Mon 2 NovArnhem Velperpoort 11:53Partial coverage0 min—
Sun 1 NovArnhem Velperpoort 11:37No data—
Sat 31 OctArnhem Velperpoort 11:370 min—
Fri 30 OctArnhem Velperpoort 11:53No data—
Thu 29 OctArnhem Velperpoort 11:530 min—
Wed 28 OctArnhem Velperpoort 11:530 min—
Tue 27 OctArnhem Velperpoort 11:530 min—
Mon 26 OctArnhem Velperpoort 11:53No data—
Fri 23 OctArnhem Velperpoort 11:53No data—
Thu 22 OctArnhem Velperpoort 11:55No data—
Wed 21 OctArnhem Velperpoort 12:03No data—
Tue 20 OctArnhem Velperpoort 11:530 min—
Mon 19 OctArnhem Velperpoort 11:53Partial coverage0 min—
Fri 16 OctArnhem Velperpoort 11:53No data—
Thu 15 OctArnhem Velperpoort 11:53No data—
Tue 13 OctArnhem Velperpoort 11:53No data—
Mon 12 OctArnhem Velperpoort 11:53No data—
Fri 9 OctArnhem Velperpoort 11:53Partial coverage0 min—
Thu 8 OctArnhem Velperpoort 11:55Partial coverage+2 min+2 min
Wed 7 OctArnhem Velperpoort 12:01No data—
Tue 6 OctArnhem Velperpoort 11:53No data—
Mon 5 OctArnhem Velperpoort 11:53No data—
Fri 2 OctArnhem Velperpoort 11:53No data—
Thu 1 OctArnhem Velperpoort 11:53No data—
Wed 30 SeptArnhem Velperpoort 11:53No data—
Tue 29 SeptArnhem Velperpoort 11:53No data—
Mon 28 SeptArnhem Velperpoort 11:55No data—
Fri 25 SeptArnhem Velperpoort 11:53No data—