Train RRReis A 31132 Arnhem Centraal → Tiel

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

RRReis A 31132 Arnhem Centraal–Tiel: final delay under 3 min on 12 of its 14 runs with data in the last 30 days (86%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 21:56 (GMT+1).

It does not run today

Last recorded run: Friday 20 November +2 min

Next service: tomorrow 13:08 from Arnhem Centraal · Mon 23 Nov

Next departure 13:08 tomorrow · Arnhem Centraal
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 0 full · 14 partial · 6 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 0 full · 20 partial · 43 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
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

  • Fri 13 Nov Max en route +5 min · last fix heading to Kesteren +5 min
  • Tue 17 Nov Max en route +3 min · last fix heading to Kesteren +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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