Train RRReis A 30744 Doetinchem – Arnhem Centraal

Doetinchem 15:38 → Arnhem Centraal 16:10 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 15:38 from Doetinchem · Fri 6 Nov

Next departure 15:38 today · Doetinchem
On-time · 30 days
75%
6/8 runs under 3 min
RT coverage: 1 full · 7 partial · 15 no data
On-time · 90 days
80%
8/10 runs under 3 min
RT coverage: 1 full · 9 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Sat 31 Oct Max en route +7 min · last fix heading to Arnhem Velperpoort +7 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Arnhem Velperpoort +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 8
  • 3–10 min 20% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 stops).

Last 90 days, 10 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
15:38on time on time
15:41— —
15:44 / 15:45— —
15:50— —
15:54 / 15:55— —
15:59— —
16:03— —
16:07— —
16: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
Thu 5 NovArnhem Velperpoort 16:22No data—
Wed 4 NovArnhem Velperpoort 16:24Partial coverage+5 min+5 min
Tue 3 NovArnhem Velperpoort 16:19No data—
Mon 2 NovArnhem Velperpoort 16:22No data—
Sun 1 NovArnhem Velperpoort 16:07No data—
Sat 31 OctArnhem Velperpoort 16:14+7 min+7 min
Fri 30 OctArnhem Velperpoort 16:24No data—
Thu 29 OctArnhem Velperpoort 16:22Partial coverage0 min—
Wed 28 OctArnhem Velperpoort 16:21Partial coverage0 min—
Tue 27 OctArnhem Velperpoort 16:23No data—
Mon 26 OctArnhem Velperpoort 16:21No data—
Fri 23 OctArnhem Velperpoort 16:25No data—
Thu 22 OctArnhem Velperpoort 16:22No data—
Wed 21 OctArnhem Velperpoort 16:21No data—
Tue 20 OctWestervoort 16:35Partial coverage0 min—
Mon 19 OctArnhem Velperpoort 16:22Partial coverage0 min—
Fri 16 OctArnhem Velperpoort 16:22No data—
Thu 15 OctArnhem Velperpoort 16:23No data—
Wed 14 OctArnhem Velperpoort 16:21No data—
Tue 13 OctArnhem Velperpoort 16:21No data—
Mon 12 OctArnhem Velperpoort 16:21Partial coverage0 min—
Fri 9 OctWehl 15:59Partial coverageNo data—
Thu 8 OctArnhem Velperpoort 16:23Partial coverage+2 min+2 min
Wed 7 OctZevenaar 16:09Partial coverageNo data—
Tue 6 OctArnhem Velperpoort 16:23Partial coverage+1 min+1 min
Mon 5 OctArnhem Velperpoort 16:23Partial coverage+2 min+2 min
Fri 2 OctArnhem Velperpoort 16:21No data—
Thu 1 OctArnhem Velperpoort 16:21No data—
Wed 30 SeptArnhem Velperpoort 16:21No data—
Tue 29 SeptArnhem Velperpoort 16:21No data—