Train RRReis A 31124 Arnhem Centraal – Tiel

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

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 11:08 from Arnhem Centraal · Fri 20 Nov

Next departure 11:08 today · Arnhem Centraal
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 0 full · 12 partial · 9 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 2 full · 14 partial · 46 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: +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

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 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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