Train RRReis A 30737 Arnhem Centraal – Zevenaar

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

✓ Today’s run finished

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

  1. Arnhem Centraal12:20
  2. Arnhem Velperpoort12:22
  3. Westervoort12:26
  4. Duiven12:30
  5. Zevenaar12:34

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

Next departure 12:20 tomorrow · Arnhem Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 6 full · 3 partial · 13 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 10 full · 3 partial · 54 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

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

  • Early 0% · 0
  • On time 100% · 13
  • 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=1
  • 100% S n=2
  • 100% S n=1

Stops and timetable

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

Last 90 days, 13 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
12:20on time on time
12:22≈ on time ≈ on time
12:26≈ on time ≈ on time
12:30≈ on time ≈ on time
12: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 12:44Partial coverage0 min—
Fri 6 NovDoetinchem De Huet 13:33No data—
Wed 4 NovDoetinchem De Huet 13:340 min—
Tue 3 NovDoetinchem De Huet 13:33No data—
Mon 2 NovDoetinchem De Huet 13:33No data—
Sun 1 NovDuiven 12:46Partial coverage+1 min+1 min
Sat 31 OctDuiven 12:45Partial coverage0 min—
Fri 30 OctDoetinchem De Huet 13:34No data—
Thu 29 OctDoetinchem De Huet 13:33No data—
Wed 28 OctDoetinchem De Huet 13:340 min—
Tue 27 OctDoetinchem De Huet 13:370 min—
Mon 26 OctDoetinchem De Huet 13:35No data—
Fri 23 OctDoetinchem De Huet 13:33No data—
Thu 22 OctDoetinchem De Huet 13:34No data—
Wed 21 OctDoetinchem De Huet 13:34No data—
Tue 20 OctDoetinchem De Huet 13:330 min—
Mon 19 OctDoetinchem De Huet 13:340 min—
Fri 16 OctDoetinchem De Huet 13:34No data—
Thu 15 OctDoetinchem De Huet 13:35No data—
Tue 13 OctDoetinchem De Huet 13:34No data—
Mon 12 OctDoetinchem De Huet 13:34No data—
Fri 9 OctDoetinchem De Huet 13:35+1 min—
Thu 8 OctDoetinchem De Huet 13:330 min—
Wed 7 OctDoetinchem De Huet 13:350 min—
Tue 6 OctDoetinchem De Huet 13:340 min—
Mon 5 OctDoetinchem De Huet 13:340 min—
Fri 2 OctDoetinchem De Huet 13:34No data—
Thu 1 OctDoetinchem De Huet 13:35No data—
Wed 30 SeptDoetinchem De Huet 13:36No data—
Tue 29 SeptDoetinchem De Huet 13:34No data—