Train RRReis A 31161 Tiel – Arnhem Centraal

Tiel 17:47 → Arnhem Centraal 18:23 Daily 0 h 36 min · 7 stops RRReis A

It has not run yet today

Last recorded run: Friday 6 November +6 min

Next service: today 17:47 from Tiel · Sat 7 Nov

Next departure 17:47 today · Tiel
On-time · 30 days
82%
9/11 runs under 3 min
RT coverage: 0 full · 11 partial · 18 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 0 full · 14 partial · 74 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Mon 2 Nov Max en route +9 min · last fix heading to Elst +9 min
  • Fri 6 Nov Max en route +6 min · last fix heading to Elst +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 12
  • 3–10 min 14% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=2
  • 100% W n=1
  • 100% T n=1
  • 50% F n=2
  • 100% S n=1
  • 100% S n=3

Stops and timetable

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

Last 90 days, 14 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
17:47on time on time
17:56— —
18:00— —
18:03— —
18:06— —
18:16— —
18:23— —

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 6 NovElst 18:29Partial coverage+6 min+6 min
Thu 5 NovZetten-Andelst 18:27No data—
Wed 4 NovZetten-Andelst 18:19No data—
Tue 3 NovZetten-Andelst 18:19No data—
Mon 2 NovElst 18:34Partial coverage+9 min+9 min
Sun 1 NovElst 18:29Partial coverage+1 min—
Sat 31 OctElst 18:30Partial coverage+1 min—
Fri 30 OctElst 18:30No data—
Thu 29 OctOpheusden 18:26No data—
Wed 28 OctZetten-Andelst 18:26Partial coverage0 min—
Tue 27 OctHemmen-Dodewaard 18:29No data—
Mon 26 OctZetten-Andelst 18:35Partial coverage+1 min+1 min
Sun 25 OctElst 18:30No data—
Sat 24 OctElst 18:33No data—
Fri 23 OctElst 18:31No data—
Thu 22 OctElst 18:30No data—
Wed 21 OctElst 18:30No data—
Tue 20 OctElst 18:30Partial coverage0 min—
Mon 19 OctElst 18:30No data—
Sun 18 OctElst 18:30Partial coverage0 min—
Sat 17 OctElst 18:30No data—
Fri 16 OctElst 18:30No data—
Thu 15 OctElst 18:30No data—
Wed 14 OctElst 18:31No data—
Tue 13 OctElst 18:30No data—
Mon 12 OctElst 18:30Partial coverage0 min—
Sun 11 OctElst 18:30Partial coverage0 min—
Sat 10 OctElst 18:30No data—
Fri 9 OctElst 18:30Partial coverage+2 min+3 min
Thu 8 OctHemmen-Dodewaard 18:17Partial coverage0 min—