Train RRReis A 31133 Tiel → Arnhem Centraal

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

RRReis A 31133 Tiel–Arnhem Centraal: final delay under 3 min on 21 of its 22 runs with data in the last 30 days (95%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 12:05 (GMT+1).

✓ Today’s run finished

Today, last fix heading to Elst at 11:29 +1 min

  1. Tiel10:47
  2. Kesteren10:56
  3. Opheusden11:00
  4. Hemmen-Dodewaard11:03
  5. Zetten-Andelst11:06
  6. Elst11:16
  7. Arnhem Centraal11:23

Next service: tomorrow 10:47 from Tiel · Mon 23 Nov

Next departure 10:47 tomorrow · Tiel
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 0 full · 22 partial · 8 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 0 full · 29 partial · 60 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: +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

  • Wed 18 Nov Max en route +12 min · last fix heading to Elst +9 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Elst +4 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Elst +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 26
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 75% W n=4
  • 67% T n=3
  • 67% F n=3
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

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