Train RRReis A 31147 Tiel – Arnhem Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 14:17 from Tiel · Fri 6 Nov

Next departure 14:17 today · Tiel
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 13 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 52 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: 0 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

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

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

On-time by weekday

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