Train RRReis A 30727 Arnhem Centraal – Zevenaar

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

Running now · updated 10:14

Heading to Zevenaar +2 min

Estimated arrival at Zevenaar 10:06 10:04

  1. Arnhem Centraal09:50
  2. Arnhem Velperpoort09:52
  3. Westervoort09:56
  4. Duiven10:00
  5. Zevenaar10:04

Today it is running worse than usual: typical arrival delay is 0 min; 100% of the last 7 runs arrived on time.

On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 6 full · 1 partial · 16 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 8 full · 1 partial · 59 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

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

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

Stops and timetable

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

Last 90 days, 9 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 10Today
09:50on time on time
09:52≈ on time ≈ on time
09:56≈ on time ≈ on time
10:00≈ on time ≈ on time
10: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 10:09Partial coverage+2 min+2 min
Sat 7 NovDuiven 10:14No data—
Fri 6 NovDoetinchem De Huet 11:04No data—
Thu 5 NovDoetinchem De Huet 11:04No data—
Wed 4 NovDoetinchem De Huet 11:040 min—
Tue 3 NovDoetinchem De Huet 11:04No data—
Mon 2 NovDoetinchem De Huet 11:04No data—
Sun 1 NovDuiven 10:110 min—
Sat 31 OctDuiven 10:14No data—
Fri 30 OctDoetinchem De Huet 11:03No data—
Thu 29 OctDoetinchem De Huet 11:04No data—
Wed 28 OctDoetinchem De Huet 11:030 min—
Tue 27 OctDoetinchem De Huet 11:040 min—
Mon 26 OctDoetinchem De Huet 11:04No data—
Fri 23 OctDoetinchem De Huet 11:05No data—
Thu 22 OctDoetinchem De Huet 11:04No data—
Wed 21 OctDoetinchem De Huet 11:04No data—
Tue 20 OctDoetinchem De Huet 11:040 min—
Mon 19 OctDoetinchem De Huet 11:050 min—
Fri 16 OctDoetinchem De Huet 11:03No data—
Thu 15 OctDoetinchem De Huet 11:03No data—
Tue 13 OctDoetinchem De Huet 11:04No data—
Mon 12 OctDoetinchem De Huet 11:04No data—
Fri 9 OctDoetinchem De Huet 11:030 min—
Thu 8 OctDoetinchem De Huet 11:03No data—
Wed 7 OctWehl 12:01No data—
Tue 6 OctDoetinchem De Huet 11:040 min—
Mon 5 OctDoetinchem De Huet 11:04No data—
Fri 2 OctDoetinchem De Huet 11:03No data—
Thu 1 OctDoetinchem De Huet 11:04No data—