Train VIAS 20026 Düsseldorf Hbf – Arnhem Centraal

Düsseldorf Hbf 15:26 → Arnhem Centraal 17:13 Daily 1 h 47 min · 20 stops VIAS

It has not run yet today

Last recorded run: Wednesday 4 November +10 min

Next service: today 15:26 from Düsseldorf Hbf · Thu 5 Nov

Next departure 15:26 today · Düsseldorf Hbf
On-time · 30 days
46%
6/13 runs under 3 min
RT coverage: 12 full · 1 partial · 16 no data
On-time · 90 days
47%
7/15 runs under 3 min
RT coverage: 14 full · 1 partial · 72 no data
Typical delay
+10min
Median at arrival, 90 days
30 days: +10 min
P90
+27min
9 in 10 runs arrive with less than this
30 days: +29 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

  • Sun 11 Oct Max en route +31 min · last fix heading to Zevenaar +31 min
  • Sat 10 Oct Max en route +32 min · last fix heading to Zevenaar +30 min
  • Sun 18 Oct Max en route +24 min · last fix heading to Zevenaar +22 min
  • Wed 7 Oct Max en route +19 min · last fix heading to Zevenaar +19 min
  • Fri 9 Oct Max en route +18 min · last fix heading to Zevenaar +18 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 47% · 7
  • 3–10 min 7% · 1
  • 10–30 min 33% · 5
  • 30+ min 13% · 2

On-time by weekday

  • 75% M n=4
  • 100% T n=3
  • 33% W n=3
  • 0% T n=1
  • 0% F n=1
  • 0% S n=1
  • 0% S n=2

Stops and timetable

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

Last 90 days, 15 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
15:26on time on time
15:32 / 15:33≈ on time ≈ +2 min
15:43 / 15:44≈ +1 min ≈ +4 min
15:49 / 15:50≈ +1 min ≈ +6 min
15:54 / 15:55≈ +2 min ≈ +7 min
15:58≈ +2 min ≈ +8 min
16:04 / 16:05≈ +2 min ≈ +10 min
16:08 / 16:09≈ +2 min ≈ +11 min
16:12≈ +3 min ≈ +12 min
16:15 / 16:19≈ +3 min ≈ +13 min
16:22≈ +3 min ≈ +15 min
16:28 / 16:29≈ +4 min ≈ +16 min
16:33≈ +4 min ≈ +17 min
16:36 / 16:37≈ +4 min ≈ +18 min
16:39≈ +4 min ≈ +19 min
16:43≈ +4 min ≈ +20 min
16:48 / 16:49≈ +5 min ≈ +21 min
16:55≈ +5 min ≈ +23 min
17:02 / 17:03≈ +5 min ≈ +25 min
17:13+6 min +28 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
Wed 4 NovZevenaar 17:37Partial coverage+10 min+10 min
Tue 3 NovZevenaar 17:24No data—
Mon 2 NovZevenaar 17:34No data—
Sun 1 NovZevenaar 17:48No data—
Sat 31 OctZevenaar 17:17No data—
Fri 30 OctZevenaar 17:17No data—
Thu 29 OctZevenaar 17:22No data—
Wed 28 OctZevenaar 17:220 min—
Tue 27 OctZevenaar 17:220 min—
Mon 26 OctZevenaar 17:220 min—
Sun 25 OctZevenaar 17:55No data—
Sat 24 OctZevenaar 17:47No data—
Fri 23 OctZevenaar 17:43No data—
Thu 22 OctZevenaar 17:18No data—
Wed 21 OctZevenaar 17:26No data—
Tue 20 OctZevenaar 17:320 min—
Mon 19 OctZevenaar 17:280 min—
Sun 18 OctZevenaar 17:40+22 min+24 min
Sat 17 OctZevenaar 17:21No data—
Fri 16 OctZevenaar 17:57No data—
Thu 15 OctZevenaar 17:17No data—
Wed 14 OctZevenaar 17:40No data—
Tue 13 OctZevenaar 17:25No data—
Mon 12 OctZevenaar 17:420 min—
Sun 11 OctZevenaar 17:47+31 min+31 min
Sat 10 OctZevenaar 17:48+30 min+32 min
Fri 9 OctZevenaar 17:21+18 min+18 min
Thu 8 OctZevenaar 17:17+14 min+14 min
Wed 7 OctZevenaar 17:17+19 min+19 min
Tue 6 OctZevenaar 17:170 min—