Train RRReis A 31117 Tiel – Arnhem Centraal

Tiel 06:47 → Arnhem Centraal 07:23 Mon, Tue, Wed, Thu, Fri 0 h 36 min · 7 stops RRReis A

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 06:47 from Tiel · Mon 9 Nov

Next departure 06:47 tomorrow · Tiel
On-time · 30 days
69%
9/13 runs under 3 min
RT coverage: 0 full · 13 partial · 7 no data
On-time · 90 days
76%
13/17 runs under 3 min
RT coverage: 0 full · 17 partial · 46 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 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

  • Tue 3 Nov Max en route +7 min · last fix heading to Elst +7 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Elst +5 min
  • Fri 30 Oct Max en route +4 min · last fix heading to Elst +4 min
  • Mon 12 Oct Max en route +4 min · last fix heading to Elst +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 13
  • 3–10 min 24% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 75% T n=4
  • 100% W n=4
  • 100% T n=3
  • 33% 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, 17 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
06:47on time +1 min
06:56— —
07:00— —
07:03— —
07:06— —
07:16— —
07: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 07:30No data—
Thu 5 NovElst 07:34No data—
Wed 4 NovElst 07:29Partial coverage+2 min+2 min
Tue 3 NovElst 07:42Partial coverage+7 min+7 min
Mon 2 NovElst 07:32No data—
Fri 30 OctElst 07:34Partial coverage+4 min+4 min
Thu 29 OctElst 07:31Partial coverage+2 min+2 min
Wed 28 OctElst 07:31Partial coverage0 min—
Tue 27 OctElst 07:32Partial coverage0 min—
Mon 26 OctElst 07:32Partial coverage+2 min+3 min
Fri 23 OctElst 07:34Partial coverage+5 min+5 min
Thu 22 OctElst 07:31Partial coverage0 min—
Wed 21 OctElst 07:30Partial coverage0 min—
Tue 20 OctElst 07:32Partial coverage0 min—
Mon 19 OctElst 07:38Partial coverage0 min—
Fri 16 OctElst 07:30No data—
Thu 15 OctElst 07:31No data—
Wed 14 OctElst 07:30Partial coverageNo data—
Tue 13 OctElst 08:01No data—
Mon 12 OctElst 07:41Partial coverage+4 min+4 min
Fri 9 OctElst 07:31Partial coverage+1 min+1 min
Thu 8 OctElst 07:31Partial coverage+1 min—
Wed 7 OctElst 07:30Partial coverage0 min—
Tue 6 OctElst 07:31Partial coverage+1 min+1 min
Mon 5 OctElst 07:32No data—
Fri 2 OctElst 07:30No data—
Thu 1 OctElst 07:31No data—
Wed 30 SeptElst 07:34No data—
Tue 29 SeptElst 07:31No data—
Mon 28 SeptElst 07:34No data—