Train RRReis A 31127 Tiel – Arnhem Centraal

Tiel 09:17 → Arnhem Centraal 09:53 Mon, Tue, Wed, Thu, Fri 0 h 36 min · 7 stops RRReis A

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 09:17 from Tiel · Mon 9 Nov

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

  • Tue 6 Oct Max en route +4 min · last fix heading to Elst +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 8
  • 3–10 min 11% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 9 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
09:17on time on time
09:26— —
09:30— —
09:33— —
09:36— —
09:46— —
09:53— —

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
Fri 6 NovElst 10:09No data—
Thu 5 NovElst 09:59No data—
Wed 4 NovElst 09:59Partial coverage+2 min+2 min
Tue 3 NovElst 10:02No data—
Mon 2 NovElst 10:02No data—
Fri 30 OctElst 10:07No data—
Thu 29 OctElst 10:02No data—
Wed 28 OctElst 10:03Partial coverage0 min—
Tue 27 OctElst 10:01Partial coverage0 min—
Mon 26 OctElst 10:01No data—
Fri 23 OctElst 10:01No data—
Thu 22 OctElst 10:04No data—
Wed 21 OctElst 10:01No data—
Tue 20 OctElst 10:00Partial coverage0 min—
Mon 19 OctElst 10:00Partial coverage0 min—
Fri 16 OctElst 10:01No data—
Thu 15 OctElst 10:03No data—
Tue 13 OctElst 10:04No data—
Mon 12 OctElst 10:02No data—
Fri 9 OctElst 10:02Partial coverage+3 min+3 min
Thu 8 OctElst 10:01Partial coverage+1 min+1 min
Wed 7 OctElst 10:02Partial coverage+2 min+2 min
Tue 6 OctElst 10:01Partial coverage+4 min+4 min
Mon 5 OctElst 10:01No data—
Fri 2 OctElst 10:01No data—
Thu 1 OctElst 10:02No data—
Wed 30 SeptElst 10:03No data—
Tue 29 SeptElst 10:04No data—
Mon 28 SeptElst 10:01No data—
Fri 25 SeptElst 10:01No data—