Train RRReis A 31125 Tiel – Arnhem Centraal

Tiel 08:47 → Arnhem Centraal 09:23 Daily 0 h 36 min · 7 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Elst at 09:29 0 min

  1. Tiel08:47
  2. Kesteren08:56
  3. Opheusden09:00
  4. Hemmen-Dodewaard09:03
  5. Zetten-Andelst09:07
  6. Elst09:16
  7. Arnhem Centraal09:23

Next service: tomorrow 08:47 from Tiel · Sun 8 Nov

Next departure 08:47 tomorrow · Tiel
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 19 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 0 full · 14 partial · 75 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: +2 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 8 Oct Max en route +3 min · last fix heading to Elst +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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