Train RRReis A 30715 Arnhem Centraal – Zevenaar

Arnhem Centraal 06:50 → Zevenaar 07:04 Mon, Tue, Wed, Thu, Fri, Sat 0 h 14 min · 5 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Duiven at 07:14 +1 min

  1. Arnhem Centraal06:50
  2. Arnhem Velperpoort06:52
  3. Westervoort06:57
  4. Duiven07:00
  5. Zevenaar07:04

Next service: Monday 06:50 from Arnhem Centraal · Mon 9 Nov

Full trip card
Next departure 06:50 Monday · Arnhem Centraal
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 12 full · 2 partial · 9 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 14 full · 2 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Zevenaar, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 23 Oct Max en route +5 min · last fix heading to Doetinchem De Huet +5 min
  • Sat 31 Oct Max en route +3 min · last fix heading to Duiven +3 min

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 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
Arnhem Centraal
06:50on time on time
Arnhem Velperpoort
06:52≈ on time ≈ on time
Westervoort
06:57≈ on time ≈ +1 min
Duiven
07:00≈ on time ≈ +2 min
Zevenaar
07:04on time +3 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
Sat 7 NovDuiven 07:14Partial coverage+1 min+1 min
Fri 6 NovDoetinchem De Huet 08:03No data—
Thu 5 NovDoetinchem De Huet 08:04No data—
Wed 4 NovDoetinchem De Huet 08:040 min—
Tue 3 NovDoetinchem De Huet 08:040 min—
Mon 2 NovDoetinchem De Huet 08:040 min—
Sat 31 OctDuiven 07:17Partial coverage+3 min+3 min
Fri 30 OctDoetinchem De Huet 08:07+3 min+3 min
Thu 29 OctDoetinchem De Huet 08:040 min—
Wed 28 OctDoetinchem De Huet 08:050 min—
Tue 27 OctDoetinchem De Huet 08:050 min—
Mon 26 OctDoetinchem De Huet 08:07+2 min+2 min
Fri 23 OctDoetinchem De Huet 08:10+5 min+5 min
Thu 22 OctDoetinchem De Huet 08:04No data—
Wed 21 OctDoetinchem De Huet 08:04No data—
Tue 20 OctDoetinchem De Huet 08:030 min—
Mon 19 OctDoetinchem De Huet 08:040 min—
Fri 16 OctDoetinchem De Huet 08:04No data—
Thu 15 OctDoetinchem De Huet 08:04No data—
Wed 14 OctDoetinchem De Huet 08:04No data—
Tue 13 OctDoetinchem De Huet 08:04No data—
Mon 12 OctDoetinchem De Huet 08:07No data—
Fri 9 OctDoetinchem De Huet 08:06+1 min+1 min
Thu 8 OctDoetinchem De Huet 08:06+1 min+1 min
Wed 7 OctDoetinchem De Huet 08:040 min—
Tue 6 OctDoetinchem De Huet 08:04No data—
Mon 5 OctDoetinchem De Huet 08:06No data—
Fri 2 OctDoetinchem De Huet 08:03No data—
Thu 1 OctDoetinchem De Huet 08:04No data—
Wed 30 SeptDoetinchem De Huet 08:05No data—