Train RRReis A 31141 Tiel – Arnhem Centraal

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

✓ Today’s run finished

Today, last fix heading to Elst at 13:29 +2 min

  1. Tiel12:47
  2. Kesteren12:56
  3. Opheusden13:00
  4. Hemmen-Dodewaard13:03
  5. Zetten-Andelst13:06
  6. Elst13:16
  7. Arnhem Centraal13:23

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

Next departure 12:47 tomorrow · Tiel
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 18 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 74 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

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 100% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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