Train RRReis A 30738 Doetinchem – Arnhem Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 14:08 from Doetinchem · Fri 6 Nov

Next departure 14:08 today · Doetinchem
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 4 full · 4 partial · 15 no data
On-time · 90 days
82%
9/11 runs under 3 min
RT coverage: 4 full · 7 partial · 56 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 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

  • Thu 8 Oct Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min
  • Wed 7 Oct Max en route +3 min · last fix heading to Arnhem Velperpoort +3 min

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 82% · 9
  • 3–10 min 18% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 67% W n=3
  • 0% T n=1
  • 100% F n=1
  • — S n=0
  • 100% S n=1

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
14:08on time on time
14:11— —
14:14 / 14:15— —
14:20— —
14:24 / 14:25— —
14:29— —
14:33— —
14:37— —
14:40— —

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
Thu 5 NovArnhem Velperpoort 14:49No data—
Wed 4 NovArnhem Velperpoort 14:54Partial coverage+3 min+3 min
Tue 3 NovArnhem Velperpoort 14:49No data—
Mon 2 NovArnhem Velperpoort 14:49No data—
Sun 1 NovArnhem Velperpoort 14:39+2 min+2 min
Sat 31 OctArnhem Velperpoort 14:36No data—
Fri 30 OctArnhem Velperpoort 14:53No data—
Thu 29 OctArnhem Velperpoort 14:54No data—
Wed 28 OctArnhem Velperpoort 14:540 min—
Tue 27 OctArnhem Velperpoort 14:540 min—
Mon 26 OctArnhem Velperpoort 14:52No data—
Fri 23 OctArnhem Velperpoort 14:55No data—
Thu 22 OctArnhem Velperpoort 14:52No data—
Wed 21 OctArnhem Velperpoort 14:51No data—
Tue 20 OctArnhem Velperpoort 14:530 min—
Mon 19 OctArnhem Velperpoort 14:51Partial coverage0 min—
Fri 16 OctArnhem Velperpoort 14:51No data—
Thu 15 OctArnhem Velperpoort 14:54No data—
Wed 14 OctArnhem Velperpoort 14:51No data—
Tue 13 OctArnhem Velperpoort 14:51No data—
Mon 12 OctArnhem Velperpoort 14:51No data—
Fri 9 OctArnhem Velperpoort 14:52Partial coverage+1 min+1 min
Thu 8 OctArnhem Velperpoort 14:55Partial coverage+4 min+4 min
Wed 7 OctArnhem Velperpoort 14:52Partial coverage+3 min+3 min
Tue 6 OctArnhem Velperpoort 14:53Partial coverage+2 min+2 min
Mon 5 OctArnhem Velperpoort 14:52Partial coverage+1 min+1 min
Fri 2 OctArnhem Velperpoort 14:52No data—
Thu 1 OctArnhem Velperpoort 14:51No data—
Wed 30 SeptArnhem Velperpoort 14:51No data—
Tue 29 SeptArnhem Velperpoort 14:51No data—