Train RRReis A 30749 Arnhem Centraal – Doetinchem

Arnhem Centraal 15:50 → Doetinchem 16:22 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 0 min

Next service: today 15:50 from Arnhem Centraal · Wed 18 Nov

Next departure 15:50 today · Arnhem Centraal
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 3 full · 4 partial · 12 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 4 full · 10 partial · 45 no data
Typical delay
0min
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 Doetinchem, 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 +8 min · last fix heading to Duiven +8 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Doetinchem De Huet +4 min

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

On-time by weekday

  • 100% M n=4
  • 67% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 0% 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
15:50on time on time
15:52— —
15:56— —
16:00— —
16:04 / 16:05— —
16:09— —
16:14 / 16:15— —
16:19— —
16:22— —

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 NovDoetinchem De Huet 16:33Partial coverage0 min—
Sun 8 NovDuiven 15:440 min—
Sat 7 NovDuiven 15:44No data—
Fri 6 NovDoetinchem De Huet 16:33No data—
Thu 5 NovDoetinchem De Huet 16:38No data—
Wed 4 NovDoetinchem De Huet 16:34Partial coverage+1 min—
Tue 3 NovDoetinchem De Huet 16:37No data—
Mon 2 NovDoetinchem De Huet 16:38No data—
Sun 1 NovDuiven 15:45No data—
Sat 31 OctDuiven 15:45+8 min+8 min
Fri 30 OctDoetinchem De Huet 16:33No data—
Thu 29 OctDoetinchem De Huet 16:35No data—
Wed 28 OctDoetinchem De Huet 16:34Partial coverage0 min—
Tue 27 OctDoetinchem De Huet 16:35Partial coverage0 min—
Mon 26 OctDoetinchem De Huet 16:34No data—
Fri 23 OctDoetinchem De Huet 16:37No data—
Thu 22 OctDoetinchem De Huet 16:35No data—
Wed 21 OctDoetinchem De Huet 16:35No data—
Tue 20 OctDoetinchem De Huet 16:370 min—
Mon 19 OctDoetinchem De Huet 16:360 min—
Fri 16 OctDoetinchem De Huet 16:35No data—
Thu 15 OctDoetinchem De Huet 16:35No data—
Tue 13 OctDoetinchem De Huet 16:34No data—
Mon 12 OctDoetinchem De Huet 16:35Partial coverage+1 min+1 min
Fri 9 OctDoetinchem De Huet 16:36Partial coverage+1 min+2 min
Thu 8 OctDoetinchem De Huet 16:35Partial coverage+1 min+2 min
Wed 7 OctDoetinchem De Huet 16:34Partial coverage0 min—
Tue 6 OctDoetinchem De Huet 16:38Partial coverage+4 min+4 min
Mon 5 OctDoetinchem De Huet 16:33Partial coverage0 min—
Fri 2 OctDoetinchem De Huet 16:33No data—