Train RRReis A 31116 Arnhem Centraal – Tiel

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

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 09:08 from Arnhem Centraal · Mon 9 Nov

Next departure 09:08 tomorrow · Arnhem Centraal
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 15 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 9
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 9 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
09:08on time on time
09:14 / 09:15— —
09:24— —
09:27— —
09:31— —
09:34— —
09: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 6 NovKesteren 09:48No data—
Thu 5 NovKesteren 09:53No data—
Wed 4 NovKesteren 09:48Partial coverage0 min—
Tue 3 NovKesteren 09:49No data—
Mon 2 NovKesteren 09:49No data—
Fri 30 OctKesteren 09:50No data—
Thu 29 OctKesteren 09:50No data—
Wed 28 OctKesteren 09:51Partial coverage0 min—
Tue 27 OctKesteren 09:49Partial coverage0 min—
Mon 26 OctKesteren 09:49No data—
Fri 23 OctKesteren 09:56No data—
Thu 22 OctKesteren 09:49No data—
Wed 21 OctKesteren 09:49No data—
Tue 20 OctKesteren 09:48Partial coverage0 min—
Mon 19 OctKesteren 09:49Partial coverage0 min—
Fri 16 OctKesteren 09:49No data—
Thu 15 OctKesteren 09:50No data—
Wed 14 OctKesteren 09:49No data—
Tue 13 OctKesteren 09:49No data—
Mon 12 OctKesteren 09:49No data—
Fri 9 OctKesteren 09:49Partial coverage0 min—
Thu 8 OctKesteren 09:51Partial coverage+3 min+3 min
Wed 7 OctKesteren 09:49Partial coverage0 min—
Tue 6 OctKesteren 09:48Partial coverage0 min—
Mon 5 OctKesteren 09:50No data—
Fri 2 OctKesteren 09:50No data—
Thu 1 OctKesteren 09:49No data—
Wed 30 SeptKesteren 09:49No data—
Tue 29 SeptKesteren 09:48No data—
Mon 28 SeptKesteren 09:48No data—