Train RRReis A 31163 Tiel → Arnhem Centraal

Tiel 18:17 → Arnhem Centraal 18:53 Mon, Tue, Wed, Thu, Fri 0 h 36 min · 7 stops RRReis A

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

It does not run today

Last recorded run: Friday 20 November +2 min

Next service: tomorrow 18:17 from Tiel · Mon 23 Nov

Next departure 18:17 tomorrow · Tiel
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 4 full · 8 partial · 5 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 6 full · 12 partial · 22 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Arnhem Centraal, 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 23 Oct Max en route +12 min · last fix heading to Elst +12 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 94% · 17
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 100% W n=2
  • 100% T n=4
  • 75% F n=4
  • — 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
18:17on time on time
18:26≈ on time ≈ on time
18:30≈ on time ≈ +1 min
18:33≈ on time ≈ +1 min
18:36≈ on time ≈ +1 min
18:46≈ on time ≈ +1 min
18:53on time +2 min

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 NovElst 19:00Partial coverage+2 min+2 min
Thu 19 NovHemmen-Dodewaard 18:54Partial coverage+1 min+1 min
Wed 18 NovZetten-Andelst 18:58Partial coverage+3 min+3 min
Tue 17 NovTiel 18:29Partial coverageNo data—
Mon 16 NovKesteren 18:55Partial coverage+1 min+1 min
Fri 13 NovElst 18:59Partial coverage+1 min—
Thu 12 NovTiel 18:29Partial coverage0 min—
Wed 11 Nov— 18:58+3 min+3 min
Tue 10 NovTiel 18:54Partial coverage+1 min—
Mon 9 Nov— 18:540 min—
Fri 6 NovElst 18:59Partial coverage+1 min—
Thu 5 Nov— 18:54No data—
Wed 4 Nov— 18:58No data—
Fri 30 OctElst 19:00No data—
Thu 29 Oct— 18:56+1 min—
Tue 27 Oct— 18:590 min—
Mon 26 Oct— 18:59No data—
Fri 23 OctElst 19:03Partial coverage+12 min+12 min
Thu 22 OctZetten-Andelst 18:57No data—
Wed 21 OctZetten-Andelst 18:57No data—
Tue 20 OctElst 19:01Partial coverage0 min—
Mon 19 OctZetten-Andelst 18:57Partial coverage0 min—
Fri 16 OctElst 19:00No data—
Thu 15 OctOpheusden 18:56No data—
Wed 14 OctElst 19:00No data—
Tue 13 OctZetten-Andelst 18:56No data—
Mon 12 OctZetten-Andelst 18:57Partial coverage0 min—
Fri 9 OctZetten-Andelst 18:50No data—
Thu 8 Oct— 18:550 min—
Mon 5 Oct— 18:560 min—