Train RRReis A 31106 Arnhem Centraal – Tiel

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

✓ Today’s run finished

Today, last fix heading to Kesteren at 07:19 +1 min

  1. Arnhem Centraal06:38
  2. Elst06:44
  3. Zetten-Andelst06:54
  4. Hemmen-Dodewaard06:57
  5. Opheusden07:00
  6. Kesteren07:04
  7. Tiel07:13

Next service: tomorrow 06:38 from Arnhem Centraal · Tue 10 Nov

Next departure 06:38 tomorrow · Arnhem Centraal
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 9 full · 8 partial · 4 no data
On-time · 90 days
86%
18/21 runs under 3 min
RT coverage: 9 full · 12 partial · 42 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: +3 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 +5 min · last fix heading to Kesteren +5 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Kesteren +4 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Kesteren +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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:38on time on time
06:44 / 06:45≈ on time ≈ on time
06:54≈ +1 min ≈ +1 min
06:57≈ +1 min ≈ +1 min
07:00≈ +1 min ≈ +1 min
07:04≈ +1 min ≈ +2 min
07:13+1 min +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
Mon 9 NovKesteren 07:19Partial coverage+1 min+1 min
Fri 6 NovKesteren 07:19No data—
Thu 5 NovKesteren 07:24No data—
Wed 4 NovKesteren 07:22Partial coverage+4 min+4 min
Tue 3 NovKesteren 07:23Partial coverage+5 min+5 min
Mon 2 NovKesteren 07:24No data—
Fri 30 OctKesteren 07:19Partial coverage0 min—
Thu 29 OctKesteren 07:20+3 min+3 min
Wed 28 OctKesteren 07:20+1 min+1 min
Tue 27 OctKesteren 07:20+2 min+2 min
Mon 26 OctKesteren 07:20+2 min+2 min
Fri 23 OctKesteren 07:21+2 min+2 min
Thu 22 OctKesteren 07:190 min—
Wed 21 OctKesteren 07:20+1 min+1 min
Tue 20 OctKesteren 07:190 min—
Mon 19 OctKesteren 07:20+1 min+1 min
Fri 16 OctKesteren 07:19Partial coverage0 min—
Thu 15 OctKesteren 07:19Partial coverage0 min—
Wed 14 OctKesteren 07:20Partial coverage+1 min+1 min
Tue 13 OctKesteren 07:20Partial coverage+1 min—
Mon 12 OctKesteren 07:18Partial coverageNo data—
Fri 9 OctKesteren 07:21Partial coverage+2 min+2 min
Thu 8 OctKesteren 07:21Partial coverage+2 min+2 min
Wed 7 OctKesteren 07:20Partial coverage+1 min+1 min
Tue 6 OctKesteren 07:23Partial coverage+4 min+4 min
Mon 5 OctKesteren 07:20No data—
Fri 2 OctKesteren 07:20No data—
Thu 1 OctKesteren 07:19No data—
Wed 30 SeptKesteren 07:18No data—
Tue 29 SeptKesteren 07:20No data—