Train RRReis A 30723 Arnhem Centraal – Zevenaar

Arnhem Centraal 08:50 → Zevenaar 09:04 Daily 0 h 14 min · 5 stops RRReis A

✓ Today’s run finished

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

  1. Arnhem Centraal08:50
  2. Arnhem Velperpoort08:52
  3. Westervoort08:56
  4. Duiven09:00
  5. Zevenaar09:04

Next service: tomorrow 08:50 from Arnhem Centraal · Mon 9 Nov

Next departure 08:50 tomorrow · Arnhem Centraal
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 8 full · 2 partial · 14 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 12 full · 2 partial · 55 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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:50on time on time
08:52≈ on time ≈ on time
08:56≈ on time ≈ on time
09:00≈ on time ≈ on time
09:04on time on time

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
Sun 8 NovDuiven 09:14Partial coverage+1 min+1 min
Sat 7 NovDuiven 09:14No data—
Fri 6 NovDoetinchem De Huet 10:04No data—
Thu 5 NovDoetinchem De Huet 10:04No data—
Wed 4 NovDoetinchem De Huet 10:040 min—
Tue 3 NovDoetinchem De Huet 10:04No data—
Mon 2 NovDoetinchem De Huet 10:04No data—
Sun 1 NovDuiven 09:15Partial coverage+1 min+1 min
Sat 31 OctDuiven 09:110 min—
Fri 30 OctDoetinchem De Huet 10:04No data—
Thu 29 OctDoetinchem De Huet 10:040 min—
Wed 28 OctDoetinchem De Huet 10:040 min—
Tue 27 OctDoetinchem De Huet 10:040 min—
Mon 26 OctDoetinchem De Huet 10:05No data—
Fri 23 OctDoetinchem De Huet 10:04No data—
Thu 22 OctDoetinchem De Huet 10:05No data—
Wed 21 OctDoetinchem De Huet 10:04No data—
Tue 20 OctDoetinchem De Huet 10:030 min—
Mon 19 OctDoetinchem De Huet 10:030 min—
Fri 16 OctDoetinchem De Huet 10:05No data—
Thu 15 OctDoetinchem De Huet 10:040 min—
Wed 14 OctDoetinchem De Huet 10:04No data—
Tue 13 OctDoetinchem De Huet 10:03No data—
Mon 12 OctDoetinchem De Huet 10:05No data—
Fri 9 OctDoetinchem De Huet 10:050 min—
Thu 8 OctDoetinchem De Huet 10:040 min—
Wed 7 OctDoetinchem De Huet 10:030 min—
Tue 6 OctDoetinchem De Huet 10:030 min—
Mon 5 OctDoetinchem De Huet 10:06No data—
Fri 2 OctDoetinchem De Huet 10:04No data—