Train RRReis A 30742 Doetinchem – Arnhem Centraal

Doetinchem 15:08 → Arnhem Centraal 15:41 Daily 0 h 33 min · 9 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Arnhem Velperpoort at 15:53 No data

  1. Doetinchem15:08
  2. Doetinchem De Huet15:11
  3. Didam15:20
  4. Zevenaar15:24
  5. Duiven15:30
  6. Arnhem Velperpoort15:39
  7. Arnhem Centraal15:41

Next service: tomorrow 15:08 from Doetinchem · Sat 7 Nov

Next departure 15:08 tomorrow · Doetinchem
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 4 full · 6 partial · 14 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 4 full · 9 partial · 54 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 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 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, 13 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
15:08on time on time
15:11— —
15:14 / 15:15— —
15:20— —
15:24 / 15:26— —
15:30— —
15:34— —
15:39— —
15:41— —

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
Fri 6 NovArnhem Velperpoort 15:53No data—
Thu 5 NovArnhem Velperpoort 15:55No data—
Wed 4 NovArnhem Velperpoort 15:54Partial coverage+1 min+1 min
Tue 3 NovArnhem Velperpoort 15:53No data—
Mon 2 NovArnhem Velperpoort 15:53No data—
Sun 1 NovArnhem Velperpoort 15:48+3 min+3 min
Sat 31 OctArnhem Velperpoort 15:450 min—
Fri 30 OctArnhem Velperpoort 15:53No data—
Thu 29 OctArnhem Velperpoort 15:53No data—
Wed 28 OctArnhem Velperpoort 15:53Partial coverage0 min—
Tue 27 OctArnhem Velperpoort 15:53Partial coverage0 min—
Mon 26 OctArnhem Velperpoort 15:53No data—
Fri 23 OctArnhem Velperpoort 15:53No data—
Thu 22 OctArnhem Velperpoort 15:53No data—
Wed 21 OctArnhem Velperpoort 15:54No data—
Tue 20 OctArnhem Velperpoort 16:240 min—
Mon 19 OctArnhem Velperpoort 15:540 min—
Fri 16 OctArnhem Velperpoort 15:54No data—
Thu 15 OctWehl 15:29No data—
Wed 14 OctDidam 15:34No data—
Tue 13 OctArnhem Velperpoort 15:53No data—
Mon 12 OctArnhem Velperpoort 15:53Partial coverage0 min—
Fri 9 OctArnhem Velperpoort 15:53Partial coverage0 min—
Thu 8 OctArnhem Velperpoort 15:53Partial coverage0 min—
Wed 7 OctArnhem Velperpoort 15:53Partial coverage0 min—
Tue 6 OctArnhem Velperpoort 15:55Partial coverage+2 min+2 min
Mon 5 OctArnhem Velperpoort 15:55Partial coverage0 min—
Fri 2 OctArnhem Velperpoort 15:53No data—
Thu 1 OctArnhem Velperpoort 15:53No data—
Wed 30 SeptArnhem Velperpoort 15:56No data—