Train RRReis A 31139 Tiel – Arnhem Centraal

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

✓ Today’s run finished

Today, last fix heading to Elst at 12:59 No data

  1. Tiel12:17
  2. Kesteren12:26
  3. Opheusden12:30
  4. Hemmen-Dodewaard12:33
  5. Zetten-Andelst12:36
  6. Elst12:46
  7. Arnhem Centraal12:53

Next service: Monday 12:17 from Tiel · Mon 9 Nov

Next departure 12:17 Monday · Tiel
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 0 full · 10 partial · 12 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 0 full · 11 partial · 53 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

  • Wed 4 Nov Max en route +9 min · last fix heading to Elst +9 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 50% W n=2
  • 100% T n=2
  • 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, 11 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:17on time on time
12:26— —
12:30— —
12:33— —
12:36— —
12:46— —
12: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 12:59No data—
Thu 5 NovElst 13:08No data—
Wed 4 NovElst 13:09Partial coverage+9 min+9 min
Tue 3 NovElst 12:59Partial coverage0 min—
Mon 2 NovElst 13:02Partial coverage0 min—
Fri 30 OctElst 13:00No data—
Thu 29 OctElst 13:01Partial coverage0 min—
Wed 28 OctElst 13:01Partial coverage0 min—
Tue 27 OctElst 13:03Partial coverage0 min—
Mon 26 OctElst 13:01No data—
Fri 23 OctElst 13:00No data—
Thu 22 OctElst 13:00No data—
Wed 21 OctElst 13:01No data—
Tue 20 OctElst 13:00Partial coverage0 min—
Mon 19 OctElst 13:00Partial coverage0 min—
Fri 16 OctElst 13:00No data—
Thu 15 OctElst 13:01No data—
Wed 14 OctElst 13:00No data—
Tue 13 OctElst 13:01No data—
Mon 12 OctElst 13:00No data—
Fri 9 OctElst 13:00Partial coverage+1 min—
Thu 8 OctElst 13:01Partial coverage+1 min—
Wed 7 OctElst 13:00No data—
Tue 6 OctElst 13:00No data—
Mon 5 OctElst 13:01Partial coverage+2 min+2 min
Fri 2 OctElst 13:00No data—
Thu 1 OctElst 13:01No data—
Wed 30 SeptElst 13:00No data—
Tue 29 SeptElst 13:00No data—
Mon 28 SeptElst 13:00No data—