Train RRReis A 31165 Tiel → Arnhem Centraal

Tiel 18:47 → Arnhem Centraal 19:24 Daily 0 h 37 min · 7 stops RRReis A

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

It has not run yet today

Last recorded run: Saturday 21 November +2 min

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

Next departure 18:47 today · Tiel
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 7 full · 6 partial · 5 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 13 full · 9 partial · 32 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
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

  • Mon 5 Oct Max en route +8 min · last fix heading to — +8 min
  • Wed 7 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=2
  • 50% W n=2
  • — T n=0
  • 100% F n=4
  • 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, 22 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
18:47on time on time
18:56≈ on time ≈ +1 min
19:00≈ on time ≈ +1 min
19:03≈ on time ≈ +2 min
19:06≈ on time ≈ +2 min
19:16≈ on time ≈ +3 min
19:24on time +4 min

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 19:32Partial coverage+2 min+2 min
Fri 20 NovElst 19:29+2 min+2 min
Sun 15 NovElst 19:32Partial coverage+2 min+2 min
Sat 14 NovElst 19:32Partial coverage+2 min+2 min
Fri 13 NovKesteren 19:090 min—
Tue 10 Nov— 19:24+1 min—
Sun 8 NovElst 19:29Partial coverage0 min—
Sat 7 NovElst 19:29Partial coverage0 min—
Fri 6 NovTiel 19:24+1 min—
Wed 4 Nov— 19:290 min—
Mon 2 Nov— 19:190 min—
Sun 1 NovElst 19:29No data—
Sat 31 OctElst 19:32Partial coverage+1 min+1 min
Fri 30 OctTiel 19:01No data—
Tue 27 Oct— 19:32No data—
Mon 26 Oct— 19:250 min—
Sun 25 OctElst 19:35No data—
Sat 24 OctElst 19:33No data—
Fri 23 OctElst 19:30No data—
Thu 22 Oct— 19:25No data—
Wed 21 Oct— 19:26No data—
Mon 19 Oct— 19:260 min—
Sun 18 OctElst 19:33Partial coverage+2 min+3 min
Sat 17 OctElst 19:30No data—
Fri 16 OctElst 19:30No data—
Wed 14 OctElst 19:30No data—
Tue 13 Oct— 19:26No data—
Mon 12 Oct— 19:270 min—
Sun 11 OctElst 19:31Partial coverage+2 min+2 min
Sat 10 OctElst 19:31Partial coverage+2 min+2 min