Train RRReis A 36916 Zevenaar – Arnhem Centraal

Zevenaar 08:45 → Arnhem Centraal 08:58 Mon, Tue, Wed, Thu 0 h 13 min · 4 stops RRReis A

It does not run today

Last recorded run: Thursday 5 November No data

Next service: Monday 08:45 from Zevenaar · Mon 9 Nov

Next departure 08:45 Monday · Zevenaar
On-time · 30 days
60%
3/5 runs under 3 min
RT coverage: 0 full · 5 partial · 7 no data
On-time · 90 days
57%
4/7 runs under 3 min
RT coverage: 0 full · 7 partial · 16 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +6 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 +10 min · last fix heading to Westervoort +10 min
  • Wed 4 Nov Max en route +8 min · last fix heading to Westervoort +8 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Westervoort +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 57% · 4
  • 3–10 min 29% · 2
  • 10–30 min 14% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 50% T n=2
  • 67% W n=3
  • 50% 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 (4 stops).

Last 90 days, 7 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:45on time +5 min
08:49— —
08:53— —
08:58— —

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 NovWestervoort 09:07No data—
Wed 4 NovWestervoort 09:14Partial coverage+8 min+8 min
Tue 3 NovWestervoort 09:09No data—
Mon 2 NovWestervoort 09:08No data—
Thu 29 OctWestervoort 09:07No data—
Wed 28 OctWestervoort 09:08Partial coverage0 min—
Tue 27 OctWestervoort 09:08Partial coverage0 min—
Mon 26 OctWestervoort 09:07No data—
Thu 15 OctWestervoort 09:07Partial coverage0 min—
Tue 13 OctWestervoort 09:07No data—
Mon 12 OctWestervoort 09:09No data—
Thu 8 OctWestervoort 09:10Partial coverage+3 min+3 min
Wed 7 OctWestervoort 09:07Partial coverage+1 min+1 min
Tue 6 OctWestervoort 09:16Partial coverage+10 min+10 min
Mon 5 OctWestervoort 09:07No data—
Thu 1 OctWestervoort 09:08No data—
Wed 30 SeptWestervoort 09:07No data—
Tue 29 SeptWestervoort 09:08No data—
Mon 28 SeptWestervoort 09:16No data—
Thu 24 SeptWestervoort 09:07No data—
Wed 23 SeptWestervoort 09:07No data—
Tue 22 SeptWestervoort 09:08No data—
Mon 21 SeptWestervoort 09:16No data—