Train RRReis A 30972 Doetinchem – Arnhem Centraal

Doetinchem 22:23 → Arnhem Centraal 22:55 Daily 0 h 32 min · 9 stops RRReis A

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 22:23 from Doetinchem · Mon 16 Nov

Next departure 22:23 today · Doetinchem
On-time · 30 days
64%
9/14 runs under 3 min
RT coverage: 12 full · 2 partial · 12 no data
On-time · 90 days
57%
12/21 runs under 3 min
RT coverage: 19 full · 2 partial · 30 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +2 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +7 min

Last 30 days

Arrival delay at Arnhem Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 2 Nov Max en route +15 min · last fix heading to — +15 min
  • Thu 12 Nov Max en route +8 min · last fix heading to — +8 min
  • Thu 8 Oct Max en route +8 min · last fix heading to — +8 min
  • Fri 16 Oct Max en route +5 min · last fix heading to — +5 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 57% · 12
  • 3–10 min 38% · 8
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=2
  • 100% W n=2
  • 0% T n=3
  • 0% F n=3
  • 67% S n=3
  • 75% S n=4

Stops and timetable

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

Last 90 days, 21 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
22:23on time on time
22:26≈ on time ≈ +1 min
22:29 / 22:30≈ +1 min ≈ +1 min
22:35≈ +1 min ≈ +3 min
22:39 / 22:40≈ +1 min ≈ +4 min
22:44≈ +2 min ≈ +5 min
22:48≈ +2 min ≈ +6 min
22:52≈ +3 min ≈ +7 min
22:55+3 min +8 min

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 15 NovArnhem Velperpoort 23:04Partial coverage0 min—
Sat 14 NovArnhem Velperpoort 23:04+4 min+4 min
Thu 12 Nov— 23:04+8 min+8 min
Wed 11 Nov— 22:58+1 min+1 min
Tue 10 Nov— 22:570 min—
Mon 9 Nov— 22:59+3 min+3 min
Sun 8 NovWehl 22:57No data—
Sat 7 NovWehl 22:440 min—
Thu 5 Nov— 22:59No data—
Tue 3 Nov— 22:59No data—
Mon 2 Nov— 23:13+15 min+15 min
Sun 1 NovWehl 22:47+3 min+3 min
Sat 31 OctWehl 22:44No data—
Fri 30 Oct— 22:58No data—
Thu 29 Oct— 23:02+4 min+4 min
Wed 28 Oct— 23:03No data—
Tue 27 Oct— 22:580 min—
Mon 26 Oct— 23:01No data—
Sun 25 OctArnhem Velperpoort 23:13No data—
Sat 24 OctDidam 23:04No data—
Fri 23 Oct— 23:02+5 min+5 min
Thu 22 Oct— 23:00No data—
Wed 21 Oct— 22:58No data—
Tue 20 Oct— 23:08No data—
Mon 19 Oct— 23:000 min—
Sun 18 OctArnhem Velperpoort 23:08Partial coverage+2 min+2 min
Sat 17 OctArnhem Velperpoort 23:06No data—
Fri 16 Oct— 23:03+5 min+5 min
Thu 15 Oct— 22:59No data—
Wed 14 Oct— 22:56No data—