Train RRReis A 30745 Arnhem Centraal – Doetinchem

Arnhem Centraal 14:50 → Doetinchem 15:22 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 0 min

Next service: today 14:50 from Arnhem Centraal · Wed 18 Nov

Next departure 14:50 today · Arnhem Centraal
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 8 full · 3 partial · 9 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 8 full · 8 partial · 45 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

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 100% · 16
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=2
  • 100% T n=2
  • — F n=0
  • 100% S n=2
  • 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
14:50on time on time
14:52≈ on time ≈ +1 min
14:56≈ on time ≈ +1 min
15:00≈ on time ≈ +1 min
15:04 / 15:05≈ on time ≈ +1 min
15:09≈ on time ≈ +1 min
15:14 / 15:15≈ on time ≈ +1 min
15:19≈ on time ≈ +2 min
15:22on 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

DateLast stopFinalMax
Tue 10 NovDoetinchem De Huet 15:34Partial coverage0 min—
Mon 9 NovDoetinchem De Huet 15:34Partial coverage0 min—
Sun 8 NovDuiven 14:47+3 min+3 min
Sat 7 NovDuiven 14:44+1 min+1 min
Fri 6 NovDoetinchem De Huet 15:34No data—
Thu 5 NovDoetinchem De Huet 15:35No data—
Wed 4 NovDoetinchem De Huet 15:34Partial coverage+2 min+2 min
Tue 3 NovDoetinchem De Huet 15:34No data—
Mon 2 NovDoetinchem De Huet 15:33No data—
Sun 1 NovDuiven 14:460 min—
Sat 31 OctDuiven 14:450 min—
Fri 30 OctDoetinchem De Huet 15:35No data—
Thu 29 OctDoetinchem De Huet 15:340 min—
Wed 28 OctDoetinchem De Huet 15:330 min—
Tue 27 OctDoetinchem De Huet 15:340 min—
Mon 26 OctDoetinchem De Huet 15:35No data—
Fri 23 OctDoetinchem De Huet 15:36No data—
Thu 22 OctDoetinchem De Huet 15:35No data—
Wed 21 OctDoetinchem De Huet 15:34No data—
Tue 20 OctDoetinchem De Huet 15:340 min—
Mon 19 OctDoetinchem De Huet 15:34Partial coverage0 min—
Fri 16 OctDoetinchem De Huet 15:35No data—
Thu 15 OctDoetinchem De Huet 15:35No data—
Wed 14 OctDoetinchem De Huet 15:33No data—
Tue 13 OctDoetinchem De Huet 15:33No data—
Mon 12 OctDoetinchem De Huet 15:33Partial coverage0 min—
Fri 9 OctDoetinchem De Huet 15:33Partial coverageNo data—
Thu 8 OctDoetinchem De Huet 15:34Partial coverage+1 min—
Wed 7 OctDoetinchem De Huet 15:33Partial coverageNo data—
Tue 6 OctDoetinchem De Huet 15:34Partial coverage0 min—