Train RRReis A 30757 Arnhem Centraal – Doetinchem

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

✓ Today’s run finished

Today, last fix heading to Didam at 18:28 No data

  1. Arnhem Centraal17:50
  2. Arnhem Velperpoort17:52
  3. Duiven18:00
  4. Zevenaar18:04
  5. Didam18:09
  6. Wehl18:14
  7. Doetinchem18:22

Next service: tomorrow 17:50 from Arnhem Centraal · Fri 6 Nov

Next departure 17:50 tomorrow · Arnhem Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 6 full · 6 partial · 12 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 6 full · 8 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

Worst days

  • Tue 6 Oct Max en route +4 min · last fix heading to Duiven +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 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 67% T n=3
  • 100% W n=2
  • 100% T n=1
  • 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
17:50on time on time
17:52≈ on time ≈ on time
17:56≈ on time ≈ on time
18:00≈ on time ≈ on time
18:04 / 18:05≈ on time ≈ on time
18:09≈ on time ≈ on time
18:14 / 18:15≈ on time ≈ on time
18:19≈ on time ≈ on time
18:22on time on time

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
Thu 5 NovDidam 18:28No data—
Wed 4 NovWehl 18:29No data—
Tue 3 NovDidam 18:23Partial coverage0 min—
Mon 2 NovDidam 18:28Partial coverage0 min—
Sun 1 NovDuiven 17:440 min—
Sat 31 OctDuiven 17:450 min—
Fri 30 OctDoetinchem De Huet 18:33No data—
Thu 29 OctDuiven 18:25No data—
Wed 28 OctDidam 18:230 min—
Tue 27 OctZevenaar 18:39No data—
Mon 26 OctDidam 18:280 min—
Fri 23 OctDoetinchem De Huet 18:36No data—
Thu 22 OctDoetinchem De Huet 18:33No data—
Wed 21 OctDoetinchem De Huet 18:33No data—
Tue 20 OctDoetinchem De Huet 18:330 min—
Mon 19 OctDoetinchem De Huet 18:330 min—
Fri 16 OctDoetinchem De Huet 18:30No data—
Thu 15 OctDoetinchem De Huet 18:33No data—
Wed 14 OctDoetinchem De Huet 18:42No data—
Tue 13 OctDoetinchem De Huet 18:33No data—
Mon 12 OctDoetinchem De Huet 18:32Partial coverage0 min—
Fri 9 OctDoetinchem De Huet 18:33Partial coverage+1 min+1 min
Thu 8 OctDuiven 18:18Partial coverage+2 min+2 min
Wed 7 OctDidam 18:23Partial coverage0 min—
Tue 6 OctDuiven 18:29Partial coverage+4 min+4 min
Mon 5 OctDidam 18:25Partial coverage+1 min—
Fri 2 OctDoetinchem De Huet 18:33No data—
Thu 1 OctZevenaar 18:19No data—
Wed 30 SeptDidam 18:18No data—
Tue 29 SeptZevenaar 18:19No data—