Train RRReis A 30730 Doetinchem – Arnhem Centraal

Doetinchem 12:08 → Arnhem Centraal 12:40 Daily 0 h 32 min · 9 stops RRReis A

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 12:08 from Doetinchem · Fri 6 Nov

Next departure 12:08 today · Doetinchem
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 2 full · 7 partial · 14 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 2 full · 10 partial · 55 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

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

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

On-time by weekday

  • 100% M n=2
  • 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, 12 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
12:08on time on time
12:11— —
12:14 / 12:15— —
12:20— —
12:24 / 12:25— —
12:29— —
12:33— —
12:37— —
12: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 NovZevenaar 12:39No data—
Wed 4 NovArnhem Velperpoort 12:53Partial coverage+1 min+2 min
Tue 3 NovArnhem Velperpoort 12:53No data—
Mon 2 NovArnhem Velperpoort 12:53No data—
Sun 1 NovArnhem Velperpoort 12:39+2 min+2 min
Sat 31 OctArnhem Velperpoort 12:37+2 min+2 min
Fri 30 OctArnhem Velperpoort 12:53No data—
Thu 29 OctArnhem Velperpoort 12:51No data—
Wed 28 OctArnhem Velperpoort 12:53Partial coverage0 min—
Tue 27 OctArnhem Velperpoort 12:52Partial coverage0 min—
Mon 26 OctArnhem Velperpoort 12:56No data—
Fri 23 OctArnhem Velperpoort 12:54No data—
Thu 22 OctArnhem Velperpoort 12:54No data—
Wed 21 OctArnhem Velperpoort 12:53No data—
Tue 20 OctArnhem Velperpoort 12:51Partial coverage0 min—
Mon 19 OctArnhem Velperpoort 12:51Partial coverage0 min—
Fri 16 OctArnhem Velperpoort 12:54No data—
Thu 15 OctArnhem Velperpoort 12:52No data—
Wed 14 OctArnhem Velperpoort 12:58No data—
Tue 13 OctArnhem Velperpoort 12:56No data—
Mon 12 OctArnhem Velperpoort 12:51No data—
Fri 9 OctArnhem Velperpoort 12:54Partial coverage+2 min+2 min
Thu 8 OctArnhem Velperpoort 12:52Partial coverage+1 min—
Wed 7 OctArnhem Velperpoort 12:52Partial coverage+1 min—
Tue 6 OctArnhem Velperpoort 12:52Partial coverage0 min—
Mon 5 OctArnhem Velperpoort 12:54Partial coverage+2 min+2 min
Fri 2 OctArnhem Velperpoort 12:51No data—
Thu 1 OctArnhem Velperpoort 12:51No data—
Wed 30 SeptArnhem Velperpoort 12:53No data—
Tue 29 SeptArnhem Velperpoort 12:52No data—