Train RRReis A 30754 Doetinchem – Arnhem Centraal

Doetinchem 18:08 → Arnhem Centraal 18:40 Daily 0 h 32 min · 9 stops RRReis A

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

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

Next departure 18:08 today · Doetinchem
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 6 full · 6 partial · 11 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 7 full · 7 partial · 44 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +7 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

Worst days

  • Thu 8 Oct Max en route +29 min · last fix heading to — +29 min
  • Fri 23 Oct Max en route +8 min · last fix heading to Arnhem Velperpoort +8 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 86% · 12
  • 3–10 min 7% · 1
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 0% T n=1
  • 50% F n=2
  • 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.

StopSched.Usually 9 days in 10
18:08on time on time
18:11≈ on time ≈ +5 min
18:14 / 18:15≈ on time ≈ +7 min
18:20≈ +1 min ≈ +9 min
18:24 / 18:25≈ +1 min ≈ +11 min
18:29≈ +1 min ≈ +12 min
18:33≈ +1 min ≈ +14 min
18:37≈ +1 min ≈ +15 min
18:40+1 min +16 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
Wed 4 NovWehl 18:44Partial coverage0 min—
Tue 3 NovDoetinchem De Huet 18:24No data—
Mon 2 NovDoetinchem 18:22No data—
Sun 1 NovArnhem Velperpoort 18:37+1 min+1 min
Sat 31 OctArnhem Velperpoort 18:37+1 min+1 min
Fri 30 OctArnhem Velperpoort 18:51No data—
Thu 29 Oct— 18:34No data—
Wed 28 OctDoetinchem De Huet 18:44Partial coverage+1 min+1 min
Tue 27 Oct— 18:460 min—
Mon 26 OctDoetinchem 18:46No data—
Fri 23 OctArnhem Velperpoort 18:51+8 min+8 min
Thu 22 OctArnhem Velperpoort 18:51No data—
Wed 21 OctWehl 18:29No data—
Tue 20 OctArnhem Velperpoort 18:500 min—
Mon 19 OctArnhem Velperpoort 18:51Partial coverage0 min—
Fri 16 OctArnhem Velperpoort 18:51No data—
Thu 15 OctDuiven 18:43No data—
Wed 14 OctArnhem Velperpoort 18:55No data—
Tue 13 OctArnhem Velperpoort 18:50No data—
Mon 12 OctArnhem Velperpoort 18:51Partial coverage0 min—
Fri 9 OctWestervoort 18:47Partial coverage+1 min+1 min
Thu 8 Oct— 19:12+29 min+29 min
Wed 7 OctDoetinchem 18:43Partial coverage0 min—
Tue 6 Oct— 18:45+2 min+2 min
Mon 5 OctDoetinchem De Huet 18:44Partial coverage+1 min+1 min
Fri 2 OctArnhem Velperpoort 18:51No data—
Wed 30 SeptDoetinchem 18:18No data—
Fri 25 SeptWestervoort 18:47No data—
Wed 23 SeptDoetinchem De Huet 18:25No data—
Mon 21 SeptDoetinchem 18:22No data—