Train RRReis A 31122 Arnhem Centraal – Tiel

Arnhem Centraal 10:38 → Tiel 11:13 Daily 0 h 35 min · 7 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Kesteren at 11:19 No data

  1. Arnhem Centraal10:38
  2. Elst10:44
  3. Zetten-Andelst10:54
  4. Hemmen-Dodewaard10:57
  5. Opheusden11:00
  6. Kesteren11:04
  7. Tiel11:13

Next service: tomorrow 10:38 from Arnhem Centraal · Fri 6 Nov

Next departure 10:38 tomorrow · Arnhem Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 18 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 76 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 Tiel, 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

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

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

Stops and timetable

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

Last 90 days, 13 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:38on time on time
10:44 / 10:45— —
10:54— —
10:57— —
11:00— —
11:04— —
11:13— —

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
Thu 5 NovKesteren 11:19No data—
Wed 4 NovKesteren 11:19Partial coverage+3 min+3 min
Tue 3 NovKesteren 11:19No data—
Mon 2 NovKesteren 11:22No data—
Sun 1 NovKesteren 11:19Partial coverage0 min—
Sat 31 OctKesteren 11:20Partial coverage+1 min+1 min
Fri 30 OctKesteren 11:22No data—
Thu 29 OctKesteren 11:21Partial coverage0 min—
Wed 28 OctKesteren 11:21Partial coverage0 min—
Tue 27 OctKesteren 11:19No data—
Mon 26 OctKesteren 11:19No data—
Sun 25 OctKesteren 11:20No data—
Sat 24 OctKesteren 11:18No data—
Fri 23 OctKesteren 11:19No data—
Thu 22 OctKesteren 11:20No data—
Wed 21 OctKesteren 11:19No data—
Tue 20 OctKesteren 11:19Partial coverage0 min—
Mon 19 OctKesteren 11:20Partial coverage0 min—
Sun 18 OctKesteren 11:18No data—
Sat 17 OctKesteren 11:19No data—
Fri 16 OctKesteren 11:18No data—
Thu 15 OctKesteren 11:19No data—
Wed 14 OctKesteren 11:23No data—
Tue 13 OctKesteren 11:21No data—
Mon 12 OctKesteren 11:20No data—
Sun 11 OctKesteren 11:20Partial coverage+1 min+1 min
Sat 10 OctKesteren 11:19Partial coverage0 min—
Fri 9 OctKesteren 11:19Partial coverage0 min—
Thu 8 OctKesteren 11:20Partial coverage+1 min—
Wed 7 OctZetten-Andelst 12:03Partial coverage0 min—