Train RRReis A 31138 Arnhem Centraal → Tiel

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

RRReis A 31138 Arnhem Centraal–Tiel: final delay under 3 min on 23 of its 23 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 23 Nov 2026, 00:41 (GMT+1).

It has not run yet today

Last recorded run: Sunday 22 November 0 min

Next service: today 14:38 from Arnhem Centraal · Mon 23 Nov

Next departure 14:38 today · Arnhem Centraal
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 0 full · 23 partial · 6 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 1 full · 30 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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 10 Oct Max en route +3 min · last fix heading to Elst +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 30
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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