Train RRReis A 31141 Tiel → Arnhem Centraal

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

RRReis A 31141 Tiel–Arnhem Centraal: final delay under 3 min on 16 of its 20 runs with data in the last 30 days (80%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 09:59 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 12:47 from Tiel · Sun 22 Nov

Next departure 12:47 today · Tiel
On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 0 full · 20 partial · 9 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 0 full · 28 partial · 59 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

  • Mon 9 Nov Max en route +8 min · last fix heading to Elst +8 min
  • Fri 13 Nov Max en route +8 min · last fix heading to Elst +7 min
  • Wed 18 Nov Max en route +5 min · last fix heading to Elst +5 min
  • Tue 17 Nov Max en route +4 min · last fix heading to Elst +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 24
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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 21 NovElst 13:29Partial coverage0 min—
Fri 20 NovElst 13:32Partial coverage+2 min+2 min
Thu 19 NovElst 13:29Partial coverage+1 min+1 min
Wed 18 NovElst 13:29Partial coverage+5 min+5 min
Tue 17 NovElst 13:33Partial coverage+4 min+4 min
Mon 16 NovElst 13:30Partial coverage+2 min+2 min
Sun 15 NovElst 13:30Partial coverage+1 min+1 min
Sat 14 NovElst 13:29Partial coverage0 min—
Fri 13 NovElst 13:34Partial coverage+7 min+8 min
Thu 12 NovElst 13:32Partial coverage+2 min+3 min
Wed 11 NovElst 13:29Partial coverage+1 min—
Tue 10 NovElst 13:29Partial coverage0 min—
Mon 9 NovElst 13:38Partial coverage+8 min+8 min
Sun 8 NovElst 13:29Partial coverage+2 min+2 min
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—