Train RRReis A 30733 Arnhem Centraal – Doetinchem

Arnhem Centraal 11:50 → Doetinchem 12:22 Daily 0 h 32 min · 9 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Duiven at 11:44 No data

  1. Arnhem Centraal11:50
  2. Arnhem Velperpoort11:52
  3. Duiven12:00
  4. Zevenaar12:04
  5. Didam12:09
  6. Doetinchem De Huet12:19
  7. Doetinchem12:22

Next service: tomorrow 11:50 from Arnhem Centraal · Mon 9 Nov

Next departure 11:50 tomorrow · Arnhem Centraal
On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 4 full · 2 partial · 18 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 4 full · 7 partial · 58 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: +4 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 10
  • 3–10 min 9% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 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, 11 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
11:50on time +1 min
11:52— —
11:56— —
12:00— —
12:04 / 12:05— —
12:09— —
12:14 / 12:15— —
12:19— —
12: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
Sun 8 NovDuiven 11:44No data—
Sat 7 NovDuiven 11:44No data—
Fri 6 NovDoetinchem De Huet 12:34No data—
Thu 5 NovDoetinchem De Huet 12:34No data—
Wed 4 NovDoetinchem De Huet 12:34Partial coverage0 min—
Tue 3 NovDoetinchem De Huet 12:34No data—
Mon 2 NovDoetinchem De Huet 12:34No data—
Sun 1 NovDuiven 11:45No data—
Sat 31 OctDuiven 11:44+8 min+8 min
Fri 30 OctDoetinchem De Huet 12:35No data—
Thu 29 OctDoetinchem De Huet 12:33No data—
Wed 28 OctDoetinchem De Huet 12:340 min—
Tue 27 OctDoetinchem De Huet 12:340 min—
Mon 26 OctDoetinchem De Huet 12:36No data—
Fri 23 OctDoetinchem De Huet 12:34No data—
Thu 22 OctDoetinchem De Huet 12:35No data—
Wed 21 OctDoetinchem De Huet 12:35No data—
Tue 20 OctDoetinchem De Huet 12:340 min—
Mon 19 OctDoetinchem De Huet 12:33Partial coverage0 min—
Fri 16 OctDoetinchem De Huet 12:34No data—
Thu 15 OctDoetinchem De Huet 12:37No data—
Wed 14 OctDoetinchem De Huet 12:34No data—
Tue 13 OctDoetinchem De Huet 12:38No data—
Mon 12 OctDoetinchem De Huet 12:33No data—
Fri 9 OctDoetinchem De Huet 12:34Partial coverage0 min—
Thu 8 OctDoetinchem De Huet 12:34Partial coverage0 min—
Wed 7 OctDoetinchem De Huet 12:33Partial coverage0 min—
Tue 6 OctDoetinchem De Huet 12:33Partial coverage0 min—
Mon 5 OctDoetinchem De Huet 12:35Partial coverage+1 min—
Fri 2 OctDoetinchem De Huet 12:33No data—