Train RRReis A 31115 Tiel – Arnhem Centraal

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

✓ Today’s run finished

Today, last fix heading to Elst at 07:02 No data

  1. Tiel06:17
  2. Kesteren06:26
  3. Opheusden06:30
  4. Hemmen-Dodewaard06:33
  5. Zetten-Andelst06:36
  6. Elst06:46
  7. Arnhem Centraal06:53

Next service: Monday 06:17 from Tiel · Mon 9 Nov

Next departure 06:17 Monday · Tiel
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 0 full · 21 partial · 1 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 0 full · 22 partial · 42 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

  • Mon 12 Oct Max en route +13 min · last fix heading to Elst +13 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Elst +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

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:02No data—
Thu 5 NovElst 06:59Partial coverage0 min—
Wed 4 NovElst 06:59Partial coverage+1 min+1 min
Tue 3 NovElst 06:59Partial coverage0 min—
Mon 2 NovElst 06:59Partial coverage0 min—
Fri 30 OctElst 07:00Partial coverage+2 min+2 min
Thu 29 OctElst 07:00Partial coverage0 min—
Wed 28 OctElst 07:01Partial coverage+1 min+1 min
Tue 27 OctElst 07:00Partial coverage0 min—
Mon 26 OctElst 07:00Partial coverage0 min—
Fri 23 OctElst 07:03Partial coverage+3 min+3 min
Thu 22 OctElst 07:01Partial coverage+1 min—
Wed 21 OctElst 07:01Partial coverage+2 min+2 min
Tue 20 OctElst 07:00Partial coverage0 min—
Mon 19 OctElst 07:00Partial coverage0 min—
Fri 16 OctElst 07:00Partial coverage0 min—
Thu 15 OctElst 07:00Partial coverage0 min—
Wed 14 OctElst 07:01Partial coverage+1 min+1 min
Tue 13 OctElst 07:01Partial coverage+1 min—
Mon 12 OctElst 07:13Partial coverage+13 min+13 min
Fri 9 OctElst 07:03Partial coverage+3 min+3 min
Thu 8 OctElst 07:01Partial coverage+1 min+1 min
Wed 7 OctElst 07:01No data—
Tue 6 OctElst 07:01Partial coverage+2 min+2 min
Mon 5 OctElst 07:01No data—
Fri 2 OctElst 07:00No data—
Thu 1 OctElst 07:01No data—
Wed 30 SeptElst 07:01No data—
Tue 29 SeptElst 07:01No data—
Mon 28 SeptElst 07:01No data—