Train RRReis A 36914 Didam – Arnhem Centraal

Didam 08:16 → Arnhem Centraal 08:29 Mon, Tue, Wed, Thu 0 h 13 min · 3 stops RRReis A

It does not run today

Last recorded run: Thursday 12 November No data

Next service: Monday 08:16 from Didam · Mon 16 Nov

Next departure 08:16 Monday · Didam
On-time · 30 days
43%
3/7 runs under 3 min
RT coverage: 1 full · 6 partial · 6 no data
On-time · 90 days
44%
4/9 runs under 3 min
RT coverage: 1 full · 8 partial · 18 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +3 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +10 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 10 Nov Max en route +12 min · last fix heading to Duiven +12 min
  • Tue 6 Oct Max en route +9 min · last fix heading to Duiven +9 min
  • Wed 4 Nov Max en route +8 min · last fix heading to Duiven +8 min
  • Mon 9 Nov Max en route +6 min · last fix heading to Duiven +6 min
  • Wed 11 Nov Max en route +3 min · last fix heading to Duiven +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 44% · 4
  • 3–10 min 44% · 4
  • 10–30 min 11% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 9 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
08:16on time +3 min
08:22— —
08:29— —

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 12 NovDuiven 08:34Partial coverageNo data—
Wed 11 NovDuiven 08:34Partial coverage+3 min+3 min
Tue 10 NovDuiven 08:44Partial coverage+12 min+12 min
Mon 9 NovDuiven 08:39Partial coverage+6 min+6 min
Thu 5 NovDuiven 08:34No data—
Wed 4 NovDuiven 08:44Partial coverage+8 min+8 min
Tue 3 NovDuiven 08:39No data—
Mon 2 NovDuiven 08:39No data—
Thu 29 OctDuiven 08:37No data—
Wed 28 OctDuiven 08:37Partial coverage0 min—
Tue 27 OctDuiven 08:39Partial coverage0 min—
Mon 26 OctDuiven 08:39No data—
Thu 15 OctDuiven 08:350 min—
Tue 13 OctDuiven 08:37No data—
Mon 12 OctDuiven 08:36No data—
Thu 8 OctDuiven 08:37Partial coverage+1 min+1 min
Wed 7 OctDuiven 08:36Partial coverageNo data—
Tue 6 OctDuiven 08:44Partial coverage+9 min+9 min
Mon 5 OctDuiven 08:40No data—
Thu 1 OctDuiven 08:40No data—
Wed 30 SeptDuiven 08:38No data—
Tue 29 SeptDuiven 08:39No data—
Mon 28 SeptDuiven 08:39No data—
Thu 24 SeptDuiven 08:39No data—
Wed 23 SeptDuiven 08:38No data—
Tue 22 SeptDuiven 08:37No data—
Mon 21 SeptDuiven 08:38No data—