Train RRReis A 30752 Doetinchem – Arnhem Centraal

Doetinchem 17:38 → Arnhem Centraal 18:10 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 9 stops RRReis A

It has not run yet today

Last recorded run: Monday 9 November +2 min

Next service: today 17:38 from Doetinchem · Thu 19 Nov

Next departure 17:38 today · Doetinchem
On-time · 30 days
75%
6/8 runs under 3 min
RT coverage: 3 full · 5 partial · 10 no data
On-time · 90 days
81%
13/16 runs under 3 min
RT coverage: 4 full · 12 partial · 42 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +6 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 6 Nov Max en route +11 min · last fix heading to Arnhem Velperpoort +11 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Westervoort +5 min
  • Sun 8 Nov Max en route +6 min · last fix heading to Arnhem Velperpoort +3 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 81% · 13
  • 3–10 min 13% · 2
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=3
  • 0% T n=1
  • 50% F n=2
  • 100% S n=1
  • 50% 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
17:38on time on time
17:41— —
17:44 / 17:45— —
17:50— —
17:54 / 17:55— —
17:59— —
18:03— —
18:07— —
18: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
Mon 9 NovArnhem Velperpoort 18:19Partial coverage+2 min+2 min
Sun 8 NovArnhem Velperpoort 18:10+3 min+6 min
Sat 7 NovArnhem Velperpoort 18:04No data—
Fri 6 NovArnhem Velperpoort 18:22Partial coverage+11 min+11 min
Thu 5 NovArnhem Velperpoort 18:19No data—
Wed 4 NovArnhem Velperpoort 18:19Partial coverage0 min—
Tue 3 NovArnhem Velperpoort 18:19No data—
Mon 2 NovArnhem Velperpoort 18:19No data—
Sun 1 NovArnhem Velperpoort 18:070 min+1 min
Sat 31 OctArnhem Velperpoort 18:08+2 min+2 min
Fri 30 OctArnhem Velperpoort 18:21No data—
Thu 29 OctDuiven 18:13No data—
Wed 28 OctArnhem Velperpoort 18:21Partial coverage0 min—
Tue 27 OctWestervoort 18:17No data—
Mon 26 OctArnhem Velperpoort 18:21Partial coverage0 min—
Fri 23 OctArnhem Velperpoort 18:22No data—
Thu 22 OctArnhem Velperpoort 18:21No data—
Wed 21 OctArnhem Velperpoort 18:21No data—
Tue 20 OctArnhem Velperpoort 18:210 min—
Mon 19 OctArnhem Velperpoort 18:21Partial coverage0 min—
Fri 16 OctArnhem Velperpoort 18:22No data—
Thu 15 OctArnhem Velperpoort 18:21No data—
Tue 13 OctArnhem Velperpoort 18:21No data—
Mon 12 OctArnhem Velperpoort 18:21Partial coverage0 min—
Fri 9 OctArnhem Velperpoort 18:21Partial coverage+1 min—
Thu 8 OctWestervoort 18:17Partial coverage+5 min+5 min
Wed 7 OctArnhem Velperpoort 18:21Partial coverage0 min—
Tue 6 OctWestervoort 18:17Partial coverage+1 min—
Mon 5 OctArnhem Velperpoort 18:21Partial coverage+1 min—
Fri 2 OctArnhem Velperpoort 18:21No data—