Train VIAS 20030 Düsseldorf Hbf – Arnhem Centraal

Düsseldorf Hbf 17:26 → Arnhem Centraal 19:14 Daily 1 h 48 min · 11 stops VIAS

It has not run yet today

Last recorded run: Sunday 1 November No data

Next service: today 17:26 from Düsseldorf Hbf · Fri 6 Nov

Next departure 17:26 today · Düsseldorf Hbf
On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 5 full · 1 partial · 5 no data
On-time · 90 days
83%
5/6 runs under 3 min
RT coverage: 5 full · 1 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +10 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 +20 min · last fix heading to Zevenaar +20 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 5
  • 3–10 min 0% · 0
  • 10–30 min 17% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 6 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:26on time +1 min
17:33≈ on time ≈ +1 min
17:43 / 17:44≈ on time ≈ +2 min
17:49 / 17:50≈ on time ≈ +3 min
17:55≈ on time ≈ +4 min
18:15 / 18:19≈ on time ≈ +6 min
18:43≈ on time ≈ +9 min
18:48 / 18:49≈ on time ≈ +9 min
18:55≈ on time ≈ +10 min
19:02 / 19:05≈ on time ≈ +11 min
19:14on time +12 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 1 NovZevenaar 19:42No data—
Sat 31 OctZevenaar 19:37No data—
Sun 25 OctZevenaar 19:48No data—
Sat 24 OctZevenaar 19:19Partial coverage0 min—
Fri 23 OctZevenaar 19:150 min+1 min
Sun 18 OctZevenaar 19:170 min—
Sat 17 OctZevenaar 19:43No data—
Fri 16 OctZevenaar 19:17No data—
Wed 14 OctZevenaar 19:170 min—
Sun 11 OctZevenaar 19:37+20 min+20 min
Sat 10 OctZevenaar 19:170 min—
Sun 4 OctZevenaar 19:26No data—
Sat 3 OctZevenaar 19:17No data—
Sun 27 SeptZevenaar 19:31No data—
Sat 26 SeptZevenaar 19:17No data—
Sun 20 SeptZevenaar 19:19No data—
Sat 19 SeptZevenaar 19:21No data—
Sun 13 SeptZevenaar 19:41No data—
Sat 12 SeptZevenaar 19:29No data—
Sun 6 SeptZevenaar 19:40No data—
Sat 5 SeptZevenaar 19:46No data—
Sun 30 AugZevenaar 19:42No data—
Sat 29 AugZevenaar 19:46No data—
Fri 28 AugZevenaar 19:17No data—
Wed 26 AugZevenaar 19:17No data—
Sun 23 AugZevenaar 19:26No data—
Sat 22 AugZevenaar 19:17No data—
Fri 21 AugZevenaar 19:23No data—
Thu 20 AugZevenaar 19:17No data—
Wed 19 AugZevenaar 19:17No data—