Train RRReis A 30710 Doetinchem – Arnhem Centraal

Doetinchem 07:08 → Arnhem Centraal 07:40 Mon, Tue, Wed, Thu, Fri, Sat 0 h 32 min · 9 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Arnhem Velperpoort at 07:57 No data

  1. Doetinchem07:08
  2. Doetinchem De Huet07:11
  3. Didam07:20
  4. Zevenaar07:24
  5. Duiven07:29
  6. Arnhem Velperpoort07:38
  7. Arnhem Centraal07:40

Next service: tomorrow 07:08 from Doetinchem · Fri 6 Nov

Next departure 07:08 tomorrow · Doetinchem
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 1 full · 18 partial · 4 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 1 full · 19 partial · 44 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: +2 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 26 Oct Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=4
  • 100% W n=3
  • 100% T n=4
  • 100% F n=4
  • 100% S n=1
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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
07:08on time on time
07:11— —
07:14 / 07:15— —
07:20— —
07:24 / 07:25— —
07:29— —
07:33— —
07:38— —
07:40— —

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 NovArnhem Velperpoort 07:57No data—
Wed 4 NovArnhem Velperpoort 07:54Partial coverage+2 min+2 min
Tue 3 NovArnhem Velperpoort 07:54Partial coverage0 min—
Mon 2 NovArnhem Velperpoort 07:53Partial coverage0 min—
Sat 31 OctArnhem Velperpoort 07:370 min—
Fri 30 OctArnhem Velperpoort 07:52Partial coverage0 min—
Thu 29 OctArnhem Velperpoort 07:56Partial coverage+1 min+1 min
Wed 28 OctArnhem Velperpoort 07:52Partial coverage0 min—
Tue 27 OctArnhem Velperpoort 07:53Partial coverage0 min—
Mon 26 OctArnhem Velperpoort 07:55Partial coverage+4 min+4 min
Fri 23 OctArnhem Velperpoort 07:52Partial coverage0 min—
Thu 22 OctArnhem Velperpoort 07:52Partial coverage0 min—
Wed 21 OctArnhem Velperpoort 07:53No data—
Tue 20 OctArnhem Velperpoort 07:53Partial coverage0 min—
Mon 19 OctArnhem Velperpoort 07:52Partial coverage0 min—
Fri 16 OctArnhem Velperpoort 07:52Partial coverage0 min—
Thu 15 OctArnhem Velperpoort 07:53Partial coverage0 min—
Wed 14 OctZevenaar 07:39Partial coverageNo data—
Tue 13 OctArnhem Velperpoort 07:55No data—
Mon 12 OctArnhem Velperpoort 07:54Partial coverage0 min—
Fri 9 OctArnhem Velperpoort 07:52Partial coverage+2 min+2 min
Thu 8 OctArnhem Velperpoort 07:53Partial coverage+1 min+1 min
Wed 7 OctArnhem Velperpoort 07:52Partial coverage0 min+1 min
Tue 6 OctArnhem Velperpoort 07:53Partial coverage+1 min+1 min
Mon 5 OctArnhem Velperpoort 07:54No data—
Fri 2 OctArnhem Velperpoort 07:52No data—
Thu 1 OctArnhem Velperpoort 07:53No data—
Wed 30 SeptArnhem Velperpoort 07:52No data—
Tue 29 SeptArnhem Velperpoort 07:55No data—
Mon 28 SeptArnhem Velperpoort 07:53No data—