Train RRReis A 30739 Arnhem Centraal – Doetinchem

Arnhem Centraal 13:20 → Doetinchem 13:52 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 9 stops RRReis A

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 13:20 from Arnhem Centraal · Thu 19 Nov

Next departure 13:20 today · Arnhem Centraal
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 2 full · 5 partial · 12 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 2 full · 12 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 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=3
  • 100% W n=3
  • 100% T n=2
  • 100% F n=1
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

Last 90 days, 14 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
13:20on time on time
13:22— —
13:26— —
13:30— —
13:34 / 13:35— —
13:39— —
13:44 / 13:45— —
13:49— —
13: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
Tue 10 NovDoetinchem De Huet 14:04Partial coverage0 min—
Mon 9 NovDoetinchem De Huet 14:04Partial coverage0 min—
Sun 8 NovDuiven 13:14No data—
Sat 7 NovDuiven 13:140 min—
Fri 6 NovDoetinchem De Huet 14:04No data—
Thu 5 NovDoetinchem De Huet 14:04No data—
Wed 4 NovDoetinchem De Huet 14:04Partial coverage0 min—
Tue 3 NovDoetinchem De Huet 14:04No data—
Mon 2 NovDoetinchem De Huet 14:03No data—
Sun 1 NovDuiven 13:130 min—
Sat 31 OctDuiven 13:23No data—
Fri 30 OctDoetinchem De Huet 14:05No data—
Thu 29 OctDoetinchem De Huet 14:03Partial coverage0 min—
Wed 28 OctDoetinchem De Huet 14:04Partial coverage0 min—
Tue 27 OctDoetinchem De Huet 14:04No data—
Mon 26 OctDoetinchem De Huet 14:03No data—
Fri 23 OctDoetinchem De Huet 14:04No data—
Thu 22 OctDoetinchem De Huet 14:04No data—
Wed 21 OctDoetinchem De Huet 14:03No data—
Tue 20 OctDoetinchem De Huet 14:05Partial coverage0 min—
Mon 19 OctDoetinchem De Huet 14:03Partial coverage0 min—
Fri 16 OctDoetinchem De Huet 14:04No data—
Thu 15 OctDoetinchem De Huet 14:05No data—
Wed 14 OctDoetinchem De Huet 14:04No data—
Tue 13 OctDoetinchem De Huet 14:04No data—
Mon 12 OctDoetinchem De Huet 14:03No data—
Fri 9 OctDoetinchem De Huet 14:04Partial coverage0 min—
Thu 8 OctDoetinchem De Huet 14:06Partial coverage+1 min+2 min
Wed 7 OctDoetinchem De Huet 14:03Partial coverage0 min—
Tue 6 OctDoetinchem De Huet 14:03Partial coverage0 min—