Train RRReis A 31104 Arnhem Centraal – Tiel

Arnhem Centraal 06:08 → Tiel 06:43 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 7 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Kesteren at 06:49 No data

  1. Arnhem Centraal06:08
  2. Elst06:14
  3. Zetten-Andelst06:24
  4. Hemmen-Dodewaard06:27
  5. Opheusden06:30
  6. Kesteren06:34
  7. Tiel06:43

Next service: Monday 06:08 from Arnhem Centraal · Mon 9 Nov

Next departure 06:08 Monday · Arnhem Centraal
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 0 full · 17 partial · 5 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 0 full · 19 partial · 45 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Tiel, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 3 Nov Max en route +10 min · last fix heading to Kesteren +10 min
  • Mon 12 Oct Max en route +8 min · last fix heading to Kesteren +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 80% T n=5
  • 100% W n=4
  • 100% T n=4
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 19 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
06:08on time on time
06:14 / 06:15— —
06:24— —
06:27— —
06:30— —
06:34— —
06:43— —

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
Fri 6 NovKesteren 06:49No data—
Thu 5 NovKesteren 06:49Partial coverage0 min—
Wed 4 NovKesteren 06:49Partial coverage+1 min+1 min
Tue 3 NovKesteren 06:59Partial coverage+10 min+10 min
Mon 2 NovKesteren 06:49No data—
Fri 30 OctKesteren 06:50Partial coverage+3 min+3 min
Thu 29 OctKesteren 06:50Partial coverage+1 min+1 min
Wed 28 OctKesteren 06:49Partial coverage+1 min+1 min
Tue 27 OctKesteren 06:50Partial coverage+1 min+1 min
Mon 26 OctKesteren 06:50Partial coverage+1 min+1 min
Fri 23 OctKesteren 06:50Partial coverage+3 min+3 min
Thu 22 OctKesteren 06:48Partial coverage0 min—
Wed 21 OctKesteren 06:50Partial coverage+2 min+2 min
Tue 20 OctKesteren 06:50Partial coverage+1 min+1 min
Mon 19 OctKesteren 06:48Partial coverage0 min—
Fri 16 OctKesteren 06:48No data—
Thu 15 OctKesteren 06:49Partial coverage+1 min+1 min
Wed 14 OctKesteren 06:48Partial coverageNo data—
Tue 13 OctKesteren 06:49Partial coverage+1 min+1 min
Mon 12 OctKesteren 06:55Partial coverage+8 min+8 min
Fri 9 OctKesteren 06:49Partial coverage0 min—
Thu 8 OctKesteren 06:48No data—
Wed 7 OctKesteren 06:49Partial coverage0 min—
Tue 6 OctKesteren 06:50Partial coverage+1 min—
Mon 5 OctKesteren 06:50No data—
Fri 2 OctKesteren 06:49No data—
Thu 1 OctKesteren 06:49No data—
Wed 30 SeptKesteren 06:50No data—
Tue 29 SeptKesteren 06:49No data—
Mon 28 SeptKesteren 06:54No data—