Train RRReis A 30723 Arnhem Centraal – Doetinchem

Arnhem Centraal 09:20 → Doetinchem 09:52 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 9 stops RRReis A

It has not run yet today

Last recorded run: Tuesday 10 November +7 min

Next service: today 09:20 from Arnhem Centraal · Thu 19 Nov

Next departure 09:20 today · Arnhem Centraal
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 3 full · 6 partial · 10 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 5 full · 11 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Doetinchem, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 10 Nov Max en route +9 min · last fix heading to Doetinchem De Huet +7 min

Distribution · 90 days

16 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 75% T n=4
  • 100% W n=3
  • 100% T n=3
  • 100% F n=1
  • 100% S n=1
  • 100% S n=2

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 stops).

Last 90 days, 16 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
09:20on time on time
09:22≈ on time ≈ +1 min
09:26≈ on time ≈ +1 min
09:30≈ on time ≈ +1 min
09:34 / 09:35≈ on time ≈ +1 min
09:39≈ on time ≈ +1 min
09:44 / 09:45≈ on time ≈ +1 min
09:49≈ on time ≈ +1 min
09:52on time +1 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

DateLast stopFinalMax
Tue 10 NovDoetinchem De Huet 10:12Partial coverage+7 min+9 min
Mon 9 NovDoetinchem De Huet 10:04Partial coverage0 min—
Sun 8 NovDuiven 09:14+1 min+1 min
Sat 7 NovDuiven 09:14No data—
Fri 6 NovDoetinchem De Huet 10:04No data—
Thu 5 NovDoetinchem De Huet 10:04No data—
Wed 4 NovDoetinchem De Huet 10:04Partial coverage0 min—
Tue 3 NovDoetinchem De Huet 10:04No data—
Mon 2 NovDoetinchem De Huet 10:04No data—
Sun 1 NovDuiven 09:15+1 min+1 min
Sat 31 OctDuiven 09:110 min—
Fri 30 OctDoetinchem De Huet 10:04No data—
Thu 29 OctDoetinchem De Huet 10:04Partial coverage0 min—
Wed 28 OctDoetinchem De Huet 10:04Partial coverage0 min—
Tue 27 OctDoetinchem De Huet 10:04Partial coverage0 min—
Mon 26 OctDoetinchem De Huet 10:05No data—
Fri 23 OctDoetinchem De Huet 10:04No data—
Thu 22 OctDoetinchem De Huet 10:05No data—
Wed 21 OctDoetinchem De Huet 10:04No data—
Tue 20 OctDoetinchem De Huet 10:030 min—
Mon 19 OctDoetinchem De Huet 10:030 min—
Fri 16 OctDoetinchem De Huet 10:05No data—
Thu 15 OctDoetinchem De Huet 10:04Partial coverage0 min—
Wed 14 OctDoetinchem De Huet 10:04No data—
Tue 13 OctDoetinchem De Huet 10:03No data—
Mon 12 OctDoetinchem De Huet 10:05No data—
Fri 9 OctDoetinchem De Huet 10:05Partial coverage0 min—
Thu 8 OctDoetinchem De Huet 10:04Partial coverage0 min—
Wed 7 OctDoetinchem De Huet 10:03Partial coverage0 min—
Tue 6 OctDoetinchem De Huet 10:03Partial coverage0 min—