Train VIAS 20009 Arnhem Centraal – Düsseldorf Hbf

Arnhem Centraal 05:45 → Düsseldorf Hbf 07:33 Mon, Tue, Wed, Thu, Fri, Sat 1 h 48 min · 20 stops VIAS

It does not run today

Last recorded run: Saturday 7 November +3 min

Next service: tomorrow 05:45 from Arnhem Centraal · Mon 9 Nov

Next departure 05:45 tomorrow · Arnhem Centraal
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 17 full · 3 partial · 5 no data
On-time · 90 days
88%
21/24 runs under 3 min
RT coverage: 21 full · 3 partial · 52 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: +8 min

Last 30 days

Arrival delay at Düsseldorf Hbf, 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 +79 min · last fix heading to Zevenaar +44 min
  • Tue 27 Oct Max en route +35 min · last fix heading to Zevenaar +35 min
  • Wed 14 Oct Max en route +5 min · last fix heading to Zevenaar +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 21
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 8% · 2

On-time by weekday

  • 100% M n=3
  • 80% T n=5
  • 80% W n=5
  • 100% T n=4
  • 67% F n=3
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 24 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
05:45on time +1 min
05:54≈ on time ≈ +2 min
06:00≈ on time ≈ +2 min
06:06 / 06:08≈ on time ≈ +3 min
06:12≈ on time ≈ +3 min
06:16≈ on time ≈ +3 min
06:18 / 06:19≈ on time ≈ +3 min
06:22≈ on time ≈ +3 min
06:26 / 06:27≈ on time ≈ +3 min
06:33≈ on time ≈ +3 min
06:37 / 06:43≈ on time ≈ +4 min
06:46 / 06:47≈ on time ≈ +4 min
06:50 / 06:51≈ on time ≈ +4 min
06:54 / 06:55≈ on time ≈ +4 min
06:59 / 07:00≈ on time ≈ +4 min
07:02 / 07:03≈ on time ≈ +4 min
07:07 / 07:08≈ on time ≈ +5 min
07:15 / 07:16≈ on time ≈ +5 min
07:24 / 07:25≈ on time ≈ +5 min
07:33on time +5 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
Sat 7 NovZevenaar 06:19Partial coverage+3 min+9 min
Fri 6 NovZevenaar 06:08No data—
Thu 5 NovZevenaar 06:09Partial coverage0 min—
Wed 4 NovZevenaar 06:09Partial coverage0 min—
Tue 3 NovZevenaar 06:090 min—
Mon 2 NovZevenaar 06:08No data—
Sat 31 OctZevenaar 06:10No data—
Fri 30 OctZevenaar 06:08No data—
Thu 29 OctZevenaar 06:40No data—
Wed 28 OctZevenaar 06:080 min—
Tue 27 OctZevenaar 06:53+35 min+35 min
Mon 26 OctZevenaar 06:130 min—
Sat 24 OctZevenaar 06:080 min—
Fri 23 OctZevenaar 07:37+44 min+79 min
Thu 22 OctZevenaar 06:090 min—
Wed 21 OctZevenaar 06:080 min—
Tue 20 OctZevenaar 06:110 min—
Mon 19 OctZevenaar 06:090 min—
Sat 17 OctZevenaar 06:080 min—
Fri 16 OctZevenaar 06:080 min—
Thu 15 OctZevenaar 06:160 min—
Wed 14 OctZevenaar 06:22+5 min+5 min
Tue 13 OctZevenaar 06:090 min—
Mon 12 OctZevenaar 06:090 min—
Sat 10 OctZevenaar 06:110 min—
Fri 9 OctZevenaar 06:080 min—
Thu 8 OctZevenaar 06:090 min—
Wed 7 OctZevenaar 06:090 min—
Tue 6 OctZevenaar 06:120 min—
Mon 5 OctZevenaar 06:09No data—