Train RRReis A 30722 Zevenaar – Arnhem Centraal

Zevenaar 10:10 → Arnhem Centraal 10:24 Daily 0 h 14 min · 5 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Arnhem Velperpoort at 10:37 +1 min

  1. Zevenaar10:10
  2. Duiven10:14
  3. Westervoort10:17
  4. Arnhem Velperpoort10:22
  5. Arnhem Centraal10:24

Next service: tomorrow 10:10 from Zevenaar · Sun 8 Nov

Next departure 10:10 tomorrow · Zevenaar
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 9 full · 3 partial · 12 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 12 full · 3 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Wed 4 Nov Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 67% W n=3
  • 100% T n=2
  • 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, 15 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
10:10on time +1 min
10:14≈ on time ≈ +1 min
10:17≈ on time ≈ +1 min
10:22≈ on time ≈ +2 min
10:24on time +2 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 NovArnhem Velperpoort 10:37Partial coverage+1 min+1 min
Fri 6 NovArnhem Velperpoort 10:49No data—
Thu 5 NovArnhem Velperpoort 10:49No data—
Wed 4 NovArnhem Velperpoort 10:54+4 min+4 min
Tue 3 NovArnhem Velperpoort 10:530 min—
Mon 2 NovArnhem Velperpoort 10:540 min—
Sun 1 NovArnhem Velperpoort 10:37Partial coverage0 min—
Sat 31 OctArnhem Velperpoort 10:37Partial coverage+1 min—
Fri 30 OctArnhem Velperpoort 10:52No data—
Thu 29 OctArnhem Velperpoort 10:510 min—
Wed 28 OctArnhem Velperpoort 10:520 min—
Tue 27 OctArnhem Velperpoort 10:520 min—
Mon 26 OctArnhem Velperpoort 10:52No data—
Fri 23 OctArnhem Velperpoort 10:57No data—
Thu 22 OctArnhem Velperpoort 10:57No data—
Wed 21 OctArnhem Velperpoort 10:51No data—
Tue 20 OctArnhem Velperpoort 10:510 min—
Mon 19 OctArnhem Velperpoort 10:520 min—
Fri 16 OctArnhem Velperpoort 10:52No data—
Thu 15 OctArnhem Velperpoort 10:52No data—
Wed 14 OctArnhem Velperpoort 10:51No data—
Tue 13 OctArnhem Velperpoort 10:52No data—
Mon 12 OctArnhem Velperpoort 10:52No data—
Fri 9 OctArnhem Velperpoort 10:54+2 min+2 min
Thu 8 OctArnhem Velperpoort 10:52+1 min—
Wed 7 OctZevenaar 12:020 min—
Tue 6 OctArnhem Velperpoort 10:510 min—
Mon 5 OctArnhem Velperpoort 10:57No data—
Fri 2 OctArnhem Velperpoort 10:52No data—
Thu 1 OctArnhem Velperpoort 10:51No data—