Train RRReis A 31129 Tiel – Arnhem Centraal

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

✓ Today’s run finished

Today, last fix heading to Elst at 10:34 +6 min

  1. Tiel09:47
  2. Kesteren09:56
  3. Opheusden10:00
  4. Hemmen-Dodewaard10:03
  5. Zetten-Andelst10:06
  6. Elst10:16
  7. Arnhem Centraal10:23

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

Next departure 09:47 tomorrow · Tiel
On-time · 30 days
72%
13/18 runs under 3 min
RT coverage: 0 full · 18 partial · 12 no data
On-time · 90 days
77%
20/26 runs under 3 min
RT coverage: 0 full · 26 partial · 63 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +7 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

  • Wed 11 Nov Max en route +11 min · last fix heading to Elst +11 min
  • Thu 12 Nov Max en route +8 min · last fix heading to Elst +8 min
  • Tue 10 Nov Max en route +6 min · last fix heading to Elst +6 min
  • Thu 19 Nov Max en route +6 min · last fix heading to Elst +6 min
  • Wed 18 Nov Max en route +5 min · last fix heading to Elst +5 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 77% · 20
  • 3–10 min 19% · 5
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 75% T n=4
  • 60% W n=5
  • 25% T n=4
  • 100% F n=2
  • 100% S n=4
  • 100% S n=4

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