Train VIAS 20021 Arnhem Centraal – Düsseldorf Hbf

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

It does not run today

Last recorded run: Sunday 8 November 0 min

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

Next departure 11:45 Monday · Arnhem Centraal
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 5 full · 3 partial · 17 no data
On-time · 90 days
87%
13/15 runs under 3 min
RT coverage: 12 full · 3 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +3 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 9 Oct Max en route +17 min · last fix heading to Zevenaar +17 min
  • Sat 7 Nov Max en route +11 min · last fix heading to Zevenaar +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 13
  • 3–10 min 7% · 1
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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