Train RRReis A 31159 Tiel – Arnhem Centraal

Tiel 17:17 → Arnhem Centraal 17: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 17:59 No data

  1. Tiel17:17
  2. Kesteren17:26
  3. Opheusden17:30
  4. Hemmen-Dodewaard17:33
  5. Zetten-Andelst17:36
  6. Elst17:46
  7. Arnhem Centraal17:53

Next service: tomorrow 17:17 from Tiel · Fri 6 Nov

Next departure 17:17 tomorrow · Tiel
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 12 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 12
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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