Train RRReis A 31148 Arnhem Centraal – Tiel

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

It does not run today

Last recorded run: Friday 6 November +1 min

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

Next departure 17:08 Monday · Arnhem Centraal
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 0 full · 8 partial · 13 no data
On-time · 90 days
83%
10/12 runs under 3 min
RT coverage: 0 full · 12 partial · 52 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 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

  • Mon 26 Oct Max en route +7 min · last fix heading to Kesteren +7 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Kesteren +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 10
  • 3–10 min 17% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=1
  • 100% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 12 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
17:08on time +1 min
17:14 / 17:15— —
17:24— —
17:27— —
17:30— —
17:34— —
17: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 17:49Partial coverage+1 min+1 min
Thu 5 NovKesteren 17:48No data—
Wed 4 NovKesteren 17:48Partial coverage0 min—
Tue 3 NovKesteren 17:48No data—
Mon 2 NovKesteren 17:48No data—
Fri 30 OctKesteren 17:48No data—
Thu 29 OctKesteren 17:48No data—
Wed 28 OctKesteren 17:48Partial coverage0 min—
Tue 27 OctKesteren 17:49No data—
Mon 26 OctKesteren 17:52Partial coverage+7 min+7 min
Fri 23 OctKesteren 17:51No data—
Thu 22 OctOpheusden 17:45No data—
Wed 21 OctKesteren 17:48No data—
Tue 20 OctKesteren 17:48Partial coverage0 min—
Mon 19 OctKesteren 17:48Partial coverage0 min—
Fri 16 OctKesteren 17:49No data—
Thu 15 OctKesteren 17:48No data—
Wed 14 OctKesteren 17:49No data—
Tue 13 OctKesteren 17:48No data—
Mon 12 OctKesteren 17:48Partial coverage0 min—
Fri 9 OctKesteren 17:48Partial coverage+2 min+2 min
Thu 8 OctKesteren 17:48Partial coverage+1 min+1 min
Wed 7 OctKesteren 17:48Partial coverage+2 min+2 min
Tue 6 OctKesteren 17:48Partial coverage+2 min+2 min
Mon 5 OctKesteren 17:50Partial coverage+4 min+4 min
Fri 2 OctKesteren 17:48No data—
Thu 1 OctKesteren 17:48No data—
Wed 30 SeptKesteren 17:48No data—
Tue 29 SeptKesteren 17:48No data—
Mon 28 SeptKesteren 17:48No data—