Train VIAS 20029 Arnhem Centraal – Düsseldorf Hbf

Arnhem Centraal 15:45 → Düsseldorf Hbf 17:33 Daily 1 h 48 min · 20 stops VIAS

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 15:45 from Arnhem Centraal · Sun 8 Nov

Next departure 15:45 today · Arnhem Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 10 full · 4 partial · 15 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 15 full · 4 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 19 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:45on time on time
15:54≈ on time ≈ on time
16:00≈ on time ≈ on time
16:06 / 16:08≈ on time ≈ on time
16:12≈ on time ≈ on time
16:16≈ on time ≈ on time
16:18 / 16:19≈ on time ≈ on time
16:22≈ on time ≈ on time
16:26 / 16:27≈ on time ≈ on time
16:33≈ on time ≈ on time
16:37 / 16:43≈ on time ≈ on time
16:46 / 16:47≈ on time ≈ on time
16:50 / 16:51≈ on time ≈ on time
16:54 / 16:55≈ on time ≈ on time
16:59 / 17:00≈ on time ≈ on time
17:02 / 17:03≈ on time ≈ on time
17:07 / 17:08≈ on time ≈ on time
17:15 / 17:16≈ on time ≈ on time
17:24 / 17:25≈ on time ≈ on time
17:33on time on time

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:08Partial coverage0 min—
Fri 6 NovZevenaar 16:09No data—
Thu 5 NovZevenaar 16:12No data—
Wed 4 NovArnhem Centraal 16:28Partial coverage0 min+20 min
Tue 3 NovZevenaar 16:09Partial coverage0 min—
Mon 2 NovZevenaar 16:14Partial coverage0 min—
Sun 1 NovZevenaar 16:10No data—
Sat 31 OctZevenaar 16:29No data—
Fri 30 OctZevenaar 16:21No data—
Thu 29 OctZevenaar 16:09No data—
Wed 28 OctZevenaar 16:090 min—
Tue 27 OctZevenaar 16:290 min—
Mon 26 OctZevenaar 16:470 min—
Sun 25 OctZevenaar 16:12No data—
Sat 24 OctZevenaar 16:160 min—
Fri 23 OctZevenaar 16:26No data—
Thu 22 OctZevenaar 16:41No data—
Wed 21 OctZevenaar 16:15No data—
Tue 20 OctZevenaar 16:130 min—
Mon 19 OctZevenaar 16:100 min—
Sun 18 OctZevenaar 16:100 min—
Sat 17 OctZevenaar 16:57No data—
Fri 16 OctZevenaar 16:11No data—
Thu 15 OctZevenaar 16:10No data—
Wed 14 OctZevenaar 16:08No data—
Tue 13 OctZevenaar 16:18No data—
Mon 12 OctZevenaar 16:090 min—
Sun 11 OctZevenaar 16:110 min—
Sat 10 OctZevenaar 16:130 min—
Fri 9 OctZevenaar 16:090 min—