Train RRReis A 31121 Tiel – Arnhem Centraal

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

✓ Today’s run finished

Today, last fix heading to Elst at 08:34 +5 min

  1. Tiel07:47
  2. Kesteren07:56
  3. Opheusden08:00
  4. Hemmen-Dodewaard08:03
  5. Zetten-Andelst08:06
  6. Elst08:16
  7. Arnhem Centraal08:23

Next service: tomorrow 07:47 from Tiel · Fri 20 Nov

Next departure 07:47 tomorrow · Tiel
On-time · 30 days
41%
7/17 runs under 3 min
RT coverage: 0 full · 17 partial · 9 no data
On-time · 90 days
54%
14/26 runs under 3 min
RT coverage: 0 full · 26 partial · 50 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +3 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +8 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

  • Thu 12 Nov Max en route +15 min · last fix heading to Elst +15 min
  • Wed 11 Nov Max en route +10 min · last fix heading to Elst +10 min
  • Tue 17 Nov Max en route +7 min · last fix heading to Elst +7 min
  • Tue 10 Nov Max en route +6 min · last fix heading to Elst +6 min
  • Tue 6 Oct Max en route +6 min · last fix heading to Elst +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 54% · 14
  • 3–10 min 38% · 10
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=4
  • 40% T n=5
  • 50% W n=6
  • 33% T n=3
  • 67% F n=3
  • 80% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 26 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
07:47on time +1 min
07:56— —
08:00— —
08:03— —
08:06— —
08:16— —
08: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
Thu 19 NovElst 08:34Partial coverage+5 min+5 min
Wed 18 NovElst 08:33Partial coverage+4 min+4 min
Tue 17 NovElst 08:34Partial coverage+7 min+7 min
Mon 16 NovElst 08:34Partial coverage+4 min+4 min
Sat 14 NovElst 08:29Partial coverage+1 min+1 min
Fri 13 NovElst 08:29Partial coverage+1 min+1 min
Thu 12 NovElst 08:44Partial coverage+15 min+15 min
Wed 11 NovElst 08:39Partial coverage+10 min+10 min
Tue 10 NovElst 08:34Partial coverage+6 min+6 min
Mon 9 NovElst 08:33Partial coverage+3 min+3 min
Sat 7 NovElst 08:29Partial coverage+2 min+2 min
Fri 6 NovElst 08:29No data—
Thu 5 NovElst 08:34No data—
Wed 4 NovElst 08:32Partial coverage+3 min+3 min
Tue 3 NovElst 08:39No data—
Mon 2 NovElst 08:29No data—
Sat 31 OctElst 08:31Partial coverage+4 min+4 min
Fri 30 OctElst 08:39No data—
Thu 29 OctElst 08:32No data—
Wed 28 OctElst 08:32Partial coverage0 min—
Tue 27 OctElst 08:35Partial coverage0 min—
Mon 26 OctElst 08:34Partial coverage0 min—
Sat 24 OctElst 08:30No data—
Fri 23 OctElst 08:31Partial coverage0 min—
Thu 22 OctElst 08:32No data—
Wed 21 OctElst 08:31No data—
Tue 20 OctElst 08:32Partial coverage0 min—
Mon 19 OctElst 08:38Partial coverage0 min—
Sat 17 OctElst 08:31Partial coverage+1 min+1 min
Fri 16 OctElst 08:31No data—