Train RRReis A 30714 Doetinchem – Arnhem Centraal

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

✓ Today’s run finished

Today, last fix heading to Arnhem Velperpoort at 08:54 +5 min

  1. Doetinchem08:08
  2. Doetinchem De Huet08:11
  3. Didam08:20
  4. Zevenaar08:24
  5. Duiven08:29
  6. Arnhem Velperpoort08:37
  7. Arnhem Centraal08:40

Next service: tomorrow 08:08 from Doetinchem · Thu 5 Nov

Next departure 08:08 tomorrow · Doetinchem
On-time · 30 days
60%
6/10 runs under 3 min
RT coverage: 0 full · 10 partial · 14 no data
On-time · 90 days
60%
6/10 runs under 3 min
RT coverage: 0 full · 10 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Tue 6 Oct Max en route +5 min · last fix heading to Arnhem Velperpoort +5 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Arnhem Velperpoort +5 min
  • Wed 7 Oct Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 60% · 6
  • 3–10 min 40% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 67% T n=3
  • 33% W n=3
  • 100% T n=2
  • 0% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

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

StopSched.
08:08
08:11
08:14 / 08:15
08:20
08:24 / 08:25
08:29
08:33
08:37
08: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.

Recent runs

DateLast stopFinalMax
Wed 4 NovArnhem Velperpoort 08:54Partial coverage+5 min+5 min
Tue 3 NovArnhem Velperpoort 08:59No data—
Mon 2 NovArnhem Velperpoort 08:54No data—
Sun 1 NovArnhem Velperpoort 08:37No data—
Sat 31 OctArnhem Velperpoort 08:36No data—
Fri 30 OctArnhem Velperpoort 08:55No data—
Thu 29 OctArnhem Velperpoort 08:53Partial coverage0 min—
Wed 28 OctArnhem Velperpoort 08:55Partial coverage0 min—
Tue 27 OctArnhem Velperpoort 08:56Partial coverage0 min—
Mon 26 OctArnhem Velperpoort 09:00No data—
Fri 23 OctArnhem Velperpoort 08:57No data—
Thu 22 OctArnhem Velperpoort 08:53No data—
Wed 21 OctArnhem Velperpoort 08:52No data—
Tue 20 OctArnhem Velperpoort 08:52Partial coverage0 min—
Mon 19 OctArnhem Velperpoort 08:52Partial coverage0 min—
Fri 16 OctArnhem Velperpoort 08:52No data—
Thu 15 OctArnhem Velperpoort 08:53No data—
Wed 14 OctArnhem Velperpoort 08:52No data—
Tue 13 OctArnhem Velperpoort 08:57No data—
Mon 12 OctArnhem Velperpoort 08:56No data—
Fri 9 OctArnhem Velperpoort 08:55Partial coverage+4 min+4 min
Thu 8 OctArnhem Velperpoort 08:52Partial coverage0 min—
Wed 7 OctArnhem Velperpoort 08:55Partial coverage+4 min+4 min
Tue 6 OctArnhem Velperpoort 08:57Partial coverage+5 min+5 min
Mon 5 OctArnhem Velperpoort 08:58No data—
Fri 2 OctArnhem Velperpoort 08:52No data—
Thu 1 OctArnhem Velperpoort 09:03No data—
Wed 30 SeptArnhem Velperpoort 08:55No data—
Tue 29 SeptArnhem Velperpoort 08:57No data—
Mon 28 SeptArnhem Velperpoort 08:55No data—