Train RRReis A 30740 Doetinchem – Arnhem Centraal

Doetinchem 14:38 → Arnhem Centraal 15:10 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 9 stops RRReis A

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 14:38 from Doetinchem · Wed 18 Nov

Next departure 14:38 today · Doetinchem
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 5 full · 5 partial · 10 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 6 full · 10 partial · 45 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 16
  • 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=4
  • 100% W n=3
  • 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, 16 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
14:38on time +1 min
14:41≈ on time ≈ +1 min
14:44 / 14:45≈ on time ≈ +1 min
14:50≈ on time ≈ +2 min
14:54 / 14:55≈ +1 min ≈ +2 min
14:59≈ +1 min ≈ +2 min
15:03≈ +1 min ≈ +2 min
15:07≈ +1 min ≈ +2 min
15:10+1 min +2 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
Tue 10 NovArnhem Velperpoort 15:19Partial coverage0 min—
Mon 9 NovArnhem Velperpoort 15:19Partial coverage0 min—
Sun 8 NovArnhem Velperpoort 15:09+2 min+3 min
Sat 7 NovArnhem Velperpoort 15:08+1 min+1 min
Fri 6 NovArnhem Velperpoort 15:19No data—
Thu 5 NovArnhem Velperpoort 15:23No data—
Wed 4 NovArnhem Velperpoort 15:24Partial coverage+2 min+2 min
Tue 3 NovArnhem Velperpoort 15:22No data—
Mon 2 NovArnhem Velperpoort 15:22No data—
Sun 1 NovArnhem Velperpoort 15:10+2 min+2 min
Sat 31 OctArnhem Velperpoort 15:070 min+1 min
Fri 30 OctArnhem Velperpoort 15:23No data—
Thu 29 OctArnhem Velperpoort 15:22No data—
Wed 28 OctArnhem Velperpoort 15:24Partial coverage0 min—
Tue 27 OctArnhem Velperpoort 15:24Partial coverage0 min—
Mon 26 OctArnhem Velperpoort 15:21No data—
Fri 23 OctArnhem Velperpoort 15:22No data—
Thu 22 OctArnhem Velperpoort 15:21No data—
Wed 21 OctArnhem Velperpoort 15:22No data—
Tue 20 OctArnhem Velperpoort 15:210 min—
Mon 19 OctArnhem Velperpoort 15:220 min—
Fri 16 OctArnhem Velperpoort 15:22No data—
Thu 15 OctArnhem Velperpoort 15:21No data—
Wed 14 OctArnhem Velperpoort 15:22No data—
Tue 13 OctArnhem Velperpoort 15:22No data—
Mon 12 OctArnhem Velperpoort 15:23No data—
Fri 9 OctArnhem Velperpoort 15:24Partial coverage+2 min+2 min
Thu 8 OctArnhem Velperpoort 15:22Partial coverage0 min+1 min
Wed 7 OctArnhem Velperpoort 15:22Partial coverage0 min+1 min
Tue 6 OctArnhem Velperpoort 15:24Partial coverage+3 min+3 min