Train RRReis A 31138 Arnhem Centraal – Tiel

Arnhem Centraal 14:38 → Tiel 15:13 Daily 0 h 35 min · 7 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Kesteren at 15:19 No data

  1. Arnhem Centraal14:38
  2. Elst14:44
  3. Zetten-Andelst14:54
  4. Hemmen-Dodewaard14:57
  5. Opheusden15:00
  6. Kesteren15:04
  7. Tiel15:13

Next service: tomorrow 14:38 from Arnhem Centraal · Sat 7 Nov

Next departure 14:38 tomorrow · Arnhem Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 1 full · 12 partial · 17 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 1 full · 14 partial · 74 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: +1 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

  • Sat 10 Oct Max en route +3 min · last fix heading to Elst +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
14:38on time on time
14:44 / 14:45— —
14:54— —
14:57— —
15:00— —
15:04— —
15:13— —

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 15:19No data—
Thu 5 NovKesteren 15:19No data—
Wed 4 NovKesteren 15:18Partial coverage0 min—
Tue 3 NovKesteren 15:18Partial coverage0 min—
Mon 2 NovKesteren 15:22No data—
Sun 1 NovKesteren 15:20Partial coverage0 min—
Sat 31 OctKesteren 15:19Partial coverage0 min—
Fri 30 OctKesteren 15:24No data—
Thu 29 OctKesteren 15:22Partial coverage0 min—
Wed 28 OctKesteren 15:19Partial coverage0 min—
Tue 27 OctKesteren 15:19Partial coverage0 min—
Mon 26 OctKesteren 15:19No data—
Sun 25 OctKesteren 15:19No data—
Sat 24 OctKesteren 15:19No data—
Fri 23 OctKesteren 15:20No data—
Thu 22 OctKesteren 15:20No data—
Wed 21 OctKesteren 15:20No data—
Tue 20 OctKesteren 15:19Partial coverage0 min—
Mon 19 OctKesteren 15:19Partial coverage0 min—
Sun 18 OctKesteren 15:18No data—
Sat 17 OctKesteren 15:19No data—
Fri 16 OctKesteren 15:19No data—
Thu 15 OctKesteren 15:19No data—
Wed 14 OctKesteren 15:19No data—
Tue 13 OctKesteren 15:19No data—
Mon 12 OctKesteren 15:19No data—
Sun 11 OctKesteren 15:19Partial coverage0 min—
Sat 10 OctElst 16:54+3 min+3 min
Fri 9 OctKesteren 15:19Partial coverage0 min—
Thu 8 OctKesteren 15:20Partial coverage+2 min+2 min