Train RRReis A 30746 Doetinchem – Arnhem Centraal

Doetinchem 16:08 → Arnhem Centraal 16:40 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 +1 min

Next service: today 16:08 from Doetinchem · Wed 18 Nov

Next departure 16:08 today · Doetinchem
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 7 full · 1 partial · 11 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 8 full · 7 partial · 45 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: +1 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=2
  • 100% T n=1
  • 100% F n=1
  • 100% S n=2
  • 100% S n=2

Stops and timetable

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

Last 90 days, 15 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
16:08on time +1 min
16:11≈ on time ≈ +1 min
16:14 / 16:15≈ on time ≈ +1 min
16:20≈ on time ≈ +1 min
16:24 / 16:25≈ on time ≈ +1 min
16:29≈ on time ≈ +1 min
16:33≈ on time ≈ +1 min
16:37≈ on time ≈ +1 min
16:40on time +1 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
Mon 9 NovArnhem Velperpoort 16:52Partial coverage+1 min+1 min
Sun 8 NovArnhem Velperpoort 16:38+1 min—
Sat 7 NovArnhem Velperpoort 16:34+1 min—
Fri 6 NovArnhem Velperpoort 16:53No data—
Thu 5 NovArnhem Velperpoort 16:52No data—
Wed 4 NovArnhem Velperpoort 16:49No data—
Tue 3 NovArnhem Velperpoort 16:54No data—
Mon 2 NovArnhem Velperpoort 16:54No data—
Sun 1 NovArnhem Velperpoort 16:37+1 min+1 min
Sat 31 OctArnhem Velperpoort 16:370 min—
Fri 30 OctArnhem Velperpoort 16:51No data—
Thu 29 OctArnhem Velperpoort 16:52No data—
Wed 28 OctArnhem Velperpoort 16:480 min—
Tue 27 OctArnhem Velperpoort 16:510 min—
Mon 26 OctArnhem Velperpoort 16:52No data—
Fri 23 OctArnhem Velperpoort 16:59No data—
Thu 22 OctArnhem Velperpoort 16:51No data—
Wed 21 OctArnhem Velperpoort 16:53No data—
Tue 20 OctArnhem Velperpoort 16:520 min—
Mon 19 OctArnhem Velperpoort 16:520 min—
Fri 16 OctArnhem Velperpoort 16:52No data—
Thu 15 OctArnhem Velperpoort 16:52No data—
Wed 14 OctArnhem Velperpoort 16:52No data—
Tue 13 OctArnhem Velperpoort 16:52No data—
Mon 12 OctArnhem Velperpoort 16:52Partial coverage0 min—
Fri 9 OctArnhem Velperpoort 16:52Partial coverage0 min—
Thu 8 OctArnhem Velperpoort 16:52Partial coverage+1 min+1 min
Wed 7 OctArnhem Velperpoort 16:52Partial coverage+1 min+1 min
Tue 6 OctArnhem Velperpoort 16:53Partial coverage+2 min+2 min
Mon 5 OctArnhem Velperpoort 16:48Partial coverage0 min—