Train RRReis A 31158 Arnhem Centraal – Tiel

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

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 19:38 from Arnhem Centraal · Sun 8 Nov

Next departure 19:38 today · Arnhem Centraal
On-time · 30 days
75%
9/12 runs under 3 min
RT coverage: 6 full · 6 partial · 10 no data
On-time · 90 days
75%
12/16 runs under 3 min
RT coverage: 10 full · 6 partial · 32 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Sat 31 Oct Max en route +6 min · last fix heading to Kesteren +6 min
  • Sat 10 Oct Max en route +6 min · last fix heading to Kesteren +6 min
  • Fri 9 Oct Max en route +3 min · last fix heading to — +3 min
  • Sun 18 Oct Max en route +3 min · last fix heading to Kesteren +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 12
  • 3–10 min 25% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=1
  • 50% F n=2
  • 33% S n=3
  • 67% S n=3

Stops and timetable

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

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