Train VIAS 20033 Arnhem Centraal – Düsseldorf Hbf

Arnhem Centraal 17:45 → Düsseldorf Hbf 19:33 Mon, Tue, Sat, Sun 1 h 48 min · 20 stops VIAS

It does not run today

Last recorded run: Monday 9 November 0 min

Next service: Monday 17:45 from Arnhem Centraal · Mon 16 Nov

Next departure 17:45 Monday · Arnhem Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 8 full · 5 partial · 16 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 14 full · 5 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

Worst days

  • Sat 24 Oct Max en route +9 min · last fix heading to Arnhem Centraal +9 min
  • Tue 6 Oct Max en route +7 min · last fix heading to Zevenaar +7 min

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 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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