Train RRReis A 30712 Doetinchem – Arnhem Centraal

Doetinchem 07:38 → Arnhem Centraal 08:10 Daily 0 h 32 min · 9 stops RRReis A

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 07:38 from Doetinchem · Sat 7 Nov

Next departure 07:38 today · Doetinchem
On-time · 30 days
78%
7/9 runs under 3 min
RT coverage: 1 full · 8 partial · 13 no data
On-time · 90 days
83%
10/12 runs under 3 min
RT coverage: 1 full · 11 partial · 54 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 9 Oct Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min
  • Fri 23 Oct Max en route +3 min · last fix heading to Arnhem Velperpoort +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 10
  • 3–10 min 17% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 0% F n=2
  • 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, 12 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
07:38on time on time
07:41— —
07:44 / 07:45— —
07:50— —
07:54 / 07:55— —
07:59— —
08:03— —
08:07— —
08:10— —

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
Fri 6 NovArnhem Velperpoort 08:24No data—
Thu 5 NovArnhem Velperpoort 08:27No data—
Wed 4 NovArnhem Velperpoort 08:24Partial coverage+2 min+2 min
Tue 3 NovArnhem Velperpoort 08:27No data—
Mon 2 NovArnhem Velperpoort 08:24No data—
Sun 1 NovArnhem Velperpoort 08:06No data—
Sat 31 OctArnhem Velperpoort 08:08+1 min+1 min
Fri 30 OctArnhem Velperpoort 08:24No data—
Thu 29 OctArnhem Velperpoort 08:24No data—
Wed 28 OctArnhem Velperpoort 08:22Partial coverage0 min—
Tue 27 OctArnhem Velperpoort 08:24Partial coverage0 min—
Mon 26 OctArnhem Velperpoort 08:24Partial coverage+2 min+2 min
Fri 23 OctArnhem Velperpoort 08:26Partial coverage+3 min+3 min
Thu 22 OctArnhem Velperpoort 08:23No data—
Wed 21 OctArnhem Velperpoort 08:22No data—
Tue 20 OctArnhem Velperpoort 08:22Partial coverage0 min—
Mon 19 OctArnhem Velperpoort 08:21Partial coverage0 min—
Fri 16 OctArnhem Velperpoort 08:22No data—
Thu 15 OctArnhem Velperpoort 08:23No data—
Tue 13 OctArnhem Velperpoort 08:24No data—
Mon 12 OctArnhem Velperpoort 08:30No data—
Fri 9 OctArnhem Velperpoort 08:26Partial coverage+4 min+4 min
Thu 8 OctArnhem Velperpoort 08:23Partial coverage+2 min+2 min
Wed 7 OctArnhem Velperpoort 08:23Partial coverage+2 min+2 min
Tue 6 OctArnhem Velperpoort 08:23Partial coverage+2 min+2 min
Mon 5 OctArnhem Velperpoort 08:24No data—
Fri 2 OctArnhem Velperpoort 08:22No data—
Thu 1 OctArnhem Velperpoort 08:24No data—
Wed 30 SeptArnhem Velperpoort 08:22No data—
Tue 29 SeptArnhem Velperpoort 08:23No data—