Train RRReis A 31137 Tiel – Arnhem Centraal

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

✓ Today’s run finished

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

  1. Tiel11:47
  2. Kesteren11:56
  3. Opheusden12:00
  4. Hemmen-Dodewaard12:03
  5. Zetten-Andelst12:06
  6. Elst12:16
  7. Arnhem Centraal12:23

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

Next departure 11:47 tomorrow · Tiel
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 0 full · 12 partial · 17 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 0 full · 16 partial · 72 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Sun 11 Oct Max en route +8 min · last fix heading to Elst +8 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Elst +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 67% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=4
  • 67% S n=3

Stops and timetable

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

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