Train RRReis A 30725 Arnhem Centraal – Doetinchem

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

✓ Today’s run finished

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

  1. Arnhem Centraal09:50
  2. Arnhem Velperpoort09:52
  3. Duiven10:00
  4. Zevenaar10:04
  5. Didam10:09
  6. Doetinchem De Huet10:19
  7. Doetinchem10:22

Next service: tomorrow 09:50 from Arnhem Centraal · Sun 8 Nov

Next departure 09:50 tomorrow · Arnhem Centraal
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 0 full · 7 partial · 17 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 59 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: +2 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

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

  • Early 0% · 0
  • On time 100% · 10
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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