Train RRReis A 31181 Tiel – Arnhem Centraal

Tiel 22:47 → Arnhem Centraal 23:23 Daily 0 h 36 min · 7 stops RRReis A

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 22:47 from Tiel · Mon 9 Nov

Next departure 22:47 today · Tiel
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 6 full · 4 partial · 14 no data
On-time · 90 days
79%
11/14 runs under 3 min
RT coverage: 10 full · 4 partial · 29 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 16 Oct Max en route +11 min · last fix heading to — +11 min
  • Sat 10 Oct Max en route +7 min · last fix heading to — +7 min
  • Thu 8 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 11
  • 3–10 min 14% · 2
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
22:47on time +3 min
22:56≈ on time ≈ +5 min
23:00≈ +1 min ≈ +5 min
23:03≈ +1 min ≈ +5 min
23:06≈ +1 min ≈ +6 min
23:16≈ +2 min ≈ +7 min
23:23+2 min +7 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
Sun 8 NovElst 23:29Partial coverage0 min—
Sat 7 NovElst 23:24Partial coverage0 min—
Fri 6 Nov— 23:28+1 min+1 min
Thu 5 Nov— 23:29No data—
Tue 3 Nov— 23:28No data—
Mon 2 Nov— 23:28+2 min+2 min
Sun 1 NovElst 23:29Partial coverage0 min—
Sat 31 OctElst 23:30No data—
Fri 30 Oct— 23:27No data—
Wed 28 Oct— 23:26No data—
Tue 27 Oct— 23:270 min—
Mon 26 Oct— 23:27No data—
Sun 25 OctElst 23:31No data—
Sat 24 Oct— 23:26No data—
Fri 23 Oct— 23:29+2 min+2 min
Thu 22 Oct— 23:27No data—
Wed 21 Oct— 23:27No data—
Tue 20 Oct— 23:30No data—
Sun 18 OctElst 23:30No data—
Sat 17 OctElst 23:33No data—
Fri 16 Oct— 23:37+11 min+11 min
Thu 15 Oct— 23:26No data—
Mon 12 Oct— 23:28+1 min—
Sun 11 OctElst 23:31Partial coverage+1 min+1 min
Sat 10 Oct— 23:33+7 min+7 min
Thu 8 Oct— 23:30+4 min+4 min
Tue 6 Oct— 23:30+3 min+3 min
Mon 5 Oct— 23:28+1 min—
Sun 4 OctElst 23:30No data—
Sat 3 OctElst 23:30No data—