Train RRReis A 31128 Arnhem Centraal → Tiel

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

RRReis A 31128 Arnhem Centraal–Tiel: final delay under 3 min on 9 of its 12 runs with data in the last 30 days (75%). Median final delay: +2 min. TrainsRadar data as of 22 Nov 2026, 09:59 (GMT+1).

It does not run today

Last recorded run: Friday 20 November +2 min

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

Next departure 12:08 tomorrow · Arnhem Centraal
On-time · 30 days
75%
9/12 runs under 3 min
RT coverage: 0 full · 12 partial · 8 no data
On-time · 90 days
83%
15/18 runs under 3 min
RT coverage: 0 full · 18 partial · 44 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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 9 Nov Max en route +8 min · last fix heading to Kesteren +8 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Kesteren +5 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Kesteren +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 75% M n=4
  • 100% T n=5
  • 75% W n=4
  • 100% T n=2
  • 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, 18 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
12:08on time on time
12:14 / 12:15— —
12:24— —
12:27— —
12:30— —
12:34— —
12: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 12:49Partial coverage+2 min+2 min
Thu 19 NovKesteren 12:49Partial coverage+1 min+1 min
Wed 18 NovKesteren 12:49Partial coverage+1 min+1 min
Tue 17 NovKesteren 12:49Partial coverage+2 min+2 min
Mon 16 NovKesteren 12:49Partial coverage+1 min+1 min
Fri 13 NovKesteren 12:53Partial coverage+5 min+5 min
Thu 12 NovKesteren 12:49Partial coverage+2 min+2 min
Wed 11 NovKesteren 12:49No data—
Tue 10 NovKesteren 12:49Partial coverage+1 min—
Mon 9 NovKesteren 12:57Partial coverage+8 min+8 min
Fri 6 NovKesteren 12:49No data—
Thu 5 NovKesteren 12:49No data—
Wed 4 NovKesteren 12:53Partial coverage+4 min+4 min
Tue 3 NovKesteren 12:49No data—
Mon 2 NovKesteren 12:49No data—
Fri 30 OctKesteren 12:49No data—
Thu 29 OctKesteren 12:50No data—
Wed 28 OctKesteren 12:50Partial coverage0 min—
Tue 27 OctKesteren 12:51Partial coverage0 min—
Mon 26 OctKesteren 12:48No data—
Fri 23 OctKesteren 12:50No data—
Thu 22 OctKesteren 12:49No data—
Wed 21 OctKesteren 12:50No data—
Tue 20 OctKesteren 12:49Partial coverage0 min—
Mon 19 OctKesteren 12:48Partial coverage0 min—
Fri 16 OctKesteren 12:53No data—
Thu 15 OctKesteren 12:50No data—
Tue 13 OctKesteren 12:50No data—
Mon 12 OctKesteren 12:53No data—
Fri 9 OctKesteren 12:49Partial coverage0 min—