Train Arriva 31163 Tiel – Arnhem Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 18:17 from Tiel · Thu 5 Nov

Next departure 18:17 today · Tiel
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 3 full · 4 partial · 10 no data
On-time · 90 days
88%
7/8 runs under 3 min
RT coverage: 4 full · 4 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 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 23 Oct Max en route +12 min · last fix heading to Elst +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 7
  • 3–10 min 0% · 0
  • 10–30 min 13% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • — W n=0
  • 100% T n=2
  • 0% 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, 8 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
18:17on time +3 min
18:26— —
18:30— —
18:33— —
18:36— —
18:46— —
18: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
Wed 4 Nov— 18:58No data—
Fri 30 OctElst 19:00No data—
Thu 29 Oct— 18:56+1 min—
Tue 27 Oct— 18:590 min—
Mon 26 Oct— 18:59No data—
Fri 23 OctElst 19:03Partial coverage+12 min+12 min
Thu 22 OctZetten-Andelst 18:57No data—
Wed 21 OctZetten-Andelst 18:57No data—
Tue 20 OctElst 19:01Partial coverage0 min—
Mon 19 OctZetten-Andelst 18:57Partial coverage0 min—
Fri 16 OctElst 19:00No data—
Thu 15 OctOpheusden 18:56No data—
Wed 14 OctElst 19:00No data—
Tue 13 OctZetten-Andelst 18:56No data—
Mon 12 OctZetten-Andelst 18:57Partial coverage0 min—
Fri 9 OctZetten-Andelst 18:50No data—
Thu 8 Oct— 18:550 min—
Mon 5 Oct— 18:560 min—
Fri 2 OctElst 19:00No data—
Fri 25 SeptHemmen-Dodewaard 18:47No data—
Fri 18 SeptElst 19:00No data—
Fri 11 SeptElst 19:00No data—
Mon 7 SeptTiel 18:31No data—
Fri 4 SeptElst 19:00No data—
Fri 28 AugElst 19:00No data—
Thu 27 AugElst 19:00No data—
Wed 26 AugElst 18:56No data—
Tue 25 AugElst 19:00No data—
Mon 24 AugKesteren 18:40No data—
Fri 21 AugElst 19:02No data—