Train VIAS 20024 Düsseldorf Hbf – Arnhem Centraal

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

It has not run yet today

Last recorded run: Saturday 7 November +15 min

Next service: today 14:26 from Düsseldorf Hbf · Sun 8 Nov

Next departure 14:26 today · Düsseldorf Hbf
On-time · 30 days
73%
8/11 runs under 3 min
RT coverage: 10 full · 1 partial · 18 no data
On-time · 90 days
56%
9/16 runs under 3 min
RT coverage: 15 full · 1 partial · 70 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+22min
9 in 10 runs arrive with less than this
30 days: +15 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

  • Wed 4 Nov Max en route +39 min · last fix heading to Zevenaar +39 min
  • Mon 5 Oct Max en route +29 min · last fix heading to Zevenaar +29 min
  • Tue 6 Oct Max en route +16 min · last fix heading to Zevenaar +16 min
  • Sat 7 Nov Max en route +15 min · last fix heading to Zevenaar +15 min
  • Thu 8 Oct Max en route +6 min · last fix heading to Zevenaar +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 56% · 9
  • 3–10 min 19% · 3
  • 10–30 min 19% · 3
  • 30+ min 6% · 1

On-time by weekday

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

Stops and timetable

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

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