Train RRReis A 31162 Arnhem Centraal – Tiel

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

✓ Today’s run finished

Today, last fix heading to Kesteren at 21:19 0 min

  1. Arnhem Centraal20:38
  2. Elst20:44
  3. Zetten-Andelst20:54
  4. Hemmen-Dodewaard20:57
  5. Opheusden21:00
  6. Kesteren21:04
  7. Tiel21:13

Next service: tomorrow 20:38 from Arnhem Centraal · Mon 9 Nov

Next departure 20:38 tomorrow · Arnhem Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 11 full · 6 partial · 10 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 13 full · 6 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

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 100% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 100% W n=1
  • 100% T n=2
  • 100% F n=2
  • 100% S n=2
  • 100% S n=4

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
20:38on time on time
20:44 / 20:45≈ on time ≈ +1 min
20:54≈ on time ≈ +1 min
20:57≈ on time ≈ +1 min
21:00≈ on time ≈ +1 min
21:04≈ on time ≈ +1 min
21:13on 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
Sun 8 NovKesteren 21:19Partial coverage0 min—
Sat 7 NovKesteren 21:19Partial coverage+3 min+3 min
Fri 6 Nov— 21:170 min—
Thu 5 Nov— 21:14No data—
Wed 4 Nov— 21:18+2 min+2 min
Mon 2 Nov— 21:18+3 min+3 min
Sun 1 NovKesteren 21:18Partial coverage0 min—
Sat 31 OctKesteren 21:20No data—
Fri 30 Oct— 21:18No data—
Thu 29 Oct— 21:17+2 min+2 min
Tue 27 Oct— 21:160 min—
Mon 26 Oct— 21:180 min—
Sun 25 OctKesteren 21:18No data—
Sat 24 OctKesteren 21:20No data—
Thu 22 Oct— 21:19No data—
Wed 21 Oct— 21:18No data—
Tue 20 Oct— 21:150 min—
Mon 19 Oct— 21:170 min—
Sun 18 OctKesteren 21:18Partial coverage0 min—
Sat 17 OctKesteren 21:18No data—
Fri 16 Oct— 21:17+1 min+1 min
Thu 15 Oct— 21:16No data—
Wed 14 Oct— 21:17No data—
Tue 13 Oct— 21:170 min—
Mon 12 Oct— 21:190 min—
Sun 11 OctKesteren 21:19Partial coverage0 min—
Sat 10 OctKesteren 21:19Partial coverage+3 min+3 min
Thu 8 Oct— 21:17+1 min—
Mon 5 Oct— 21:17+1 min—
Sun 4 OctKesteren 21:20No data—