Train RRReis A 30743 Arnhem Centraal – Doetinchem

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

✓ Today’s run finished

Today, last fix heading to Doetinchem De Huet at 15:04 No data

  1. Arnhem Centraal14:20
  2. Arnhem Velperpoort14:22
  3. Duiven14:30
  4. Zevenaar14:34
  5. Didam14:39
  6. Doetinchem De Huet14:49
  7. Doetinchem14:52

Next service: tomorrow 14:20 from Arnhem Centraal · Sat 7 Nov

Next departure 14:20 tomorrow · Arnhem Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 4 full · 5 partial · 15 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 4 full · 8 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Doetinchem, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

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 100% · 12
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • — S n=0
  • — 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
14:20on time on time
14:22— —
14:26— —
14:30— —
14:34 / 14:35— —
14:39— —
14:44 / 14:45— —
14:49— —
14:52— —

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 NovDoetinchem De Huet 15:04No data—
Thu 5 NovDoetinchem De Huet 15:04No data—
Wed 4 NovDoetinchem De Huet 15:04Partial coverage+1 min+1 min
Tue 3 NovDoetinchem De Huet 15:04Partial coverage0 min—
Mon 2 NovDoetinchem De Huet 15:04Partial coverage0 min—
Sun 1 NovDuiven 14:15No data—
Sat 31 OctDuiven 14:14No data—
Fri 30 OctDoetinchem De Huet 15:08No data—
Thu 29 OctDoetinchem De Huet 15:04No data—
Wed 28 OctDoetinchem De Huet 15:090 min—
Tue 27 OctDoetinchem De Huet 15:060 min—
Mon 26 OctDoetinchem De Huet 15:04No data—
Fri 23 OctDoetinchem De Huet 15:05No data—
Thu 22 OctDoetinchem De Huet 15:05No data—
Wed 21 OctDoetinchem De Huet 15:04No data—
Tue 20 OctDoetinchem De Huet 15:030 min—
Mon 19 OctDoetinchem De Huet 15:050 min—
Fri 16 OctDoetinchem De Huet 15:05No data—
Thu 15 OctDoetinchem De Huet 15:03No data—
Wed 14 OctDoetinchem De Huet 15:04No data—
Tue 13 OctDoetinchem De Huet 15:05No data—
Mon 12 OctDoetinchem De Huet 15:05No data—
Fri 9 OctDoetinchem De Huet 15:06Partial coverage+1 min+2 min
Thu 8 OctDoetinchem De Huet 15:04Partial coverage0 min—
Wed 7 OctDoetinchem De Huet 15:05Partial coverage+1 min—
Tue 6 OctDoetinchem De Huet 15:07Partial coverage+2 min+2 min
Mon 5 OctDoetinchem De Huet 15:05Partial coverage+1 min+1 min
Fri 2 OctDoetinchem De Huet 15:03No data—
Thu 1 OctDoetinchem De Huet 15:03No data—
Wed 30 SeptDoetinchem De Huet 15:04No data—