Train RRReis A 30717 Arnhem Centraal – Zevenaar

Arnhem Centraal 07:20 → Zevenaar 07:34 Daily 0 h 14 min · 5 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Duiven at 07:44 0 min

  1. Arnhem Centraal07:20
  2. Arnhem Velperpoort07:22
  3. Westervoort07:26
  4. Duiven07:30
  5. Zevenaar07:34

Next service: tomorrow 07:20 from Arnhem Centraal · Sun 8 Nov

Next departure 07:20 tomorrow · Arnhem Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 8 full · 1 partial · 14 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 11 full · 1 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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=2
  • 100% S n=1
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
07:20on time on time
07:22≈ on time ≈ on time
07:26≈ on time ≈ on time
07:30≈ on time ≈ +1 min
07:34on time +1 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:44Partial coverage0 min—
Fri 6 NovDoetinchem De Huet 08:34No data—
Thu 5 NovDoetinchem De Huet 08:34No data—
Wed 4 NovDoetinchem De Huet 08:340 min—
Tue 3 NovDoetinchem De Huet 08:37No data—
Mon 2 NovDoetinchem De Huet 08:34No data—
Sun 1 NovDuiven 07:44No data—
Sat 31 OctDuiven 07:44No data—
Fri 30 OctDoetinchem De Huet 08:34No data—
Thu 29 OctDoetinchem De Huet 08:33No data—
Wed 28 OctDoetinchem De Huet 08:330 min—
Tue 27 OctDoetinchem De Huet 08:360 min—
Mon 26 OctDoetinchem De Huet 08:350 min—
Fri 23 OctDoetinchem De Huet 08:350 min—
Thu 22 OctDoetinchem De Huet 08:34No data—
Wed 21 OctDoetinchem De Huet 08:34No data—
Tue 20 OctDoetinchem De Huet 08:340 min—
Mon 19 OctDoetinchem De Huet 08:340 min—
Fri 16 OctDoetinchem De Huet 08:33No data—
Thu 15 OctDoetinchem De Huet 08:35No data—
Tue 13 OctDoetinchem De Huet 08:38No data—
Mon 12 OctDoetinchem De Huet 08:35No data—
Fri 9 OctDoetinchem De Huet 08:37+2 min+2 min
Thu 8 OctDoetinchem De Huet 08:340 min—
Wed 7 OctDoetinchem De Huet 08:340 min—
Tue 6 OctDoetinchem De Huet 08:35+1 min+1 min
Mon 5 OctDoetinchem De Huet 08:35No data—
Fri 2 OctDoetinchem De Huet 08:33No data—
Thu 1 OctDoetinchem De Huet 08:37No data—
Wed 30 SeptDoetinchem De Huet 08:36No data—