Train VIAS 20032 Düsseldorf Hbf – Arnhem Centraal

Düsseldorf Hbf 18:26 → Arnhem Centraal 20:13 Mon, Tue, Sat, Sun 1 h 47 min · 20 stops VIAS

It does not run today

Last recorded run: Sunday 8 November +23 min

Next service: Monday 18:26 from Düsseldorf Hbf · Mon 16 Nov

Next departure 18:26 Monday · Düsseldorf Hbf
On-time · 30 days
33%
1/3 runs under 3 min
RT coverage: 1 full · 2 partial · 5 no data
On-time · 90 days
20%
1/5 runs under 3 min
RT coverage: 3 full · 2 partial · 24 no data
Typical delay
+15min
Median at arrival, 90 days
P90
+32min
9 in 10 runs arrive with less than this

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

  • Sat 7 Nov Max en route +38 min · last fix heading to Zevenaar +37 min
  • Sun 8 Nov Max en route +23 min · last fix heading to Zevenaar +23 min
  • Sun 11 Oct Max en route +15 min · last fix heading to Zevenaar +15 min
  • Sat 10 Oct Max en route +7 min · last fix heading to Zevenaar +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 20% · 1
  • 3–10 min 20% · 1
  • 10–30 min 40% · 2
  • 30+ min 20% · 1

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 0% S n=2
  • 33% S n=3

Stops and timetable

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

Last 90 days, 5 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
18:26on time +19 min
18:32 / 18:33— —
18:43 / 18:44— —
18:49 / 18:50— —
18:54 / 18:55— —
18:58— —
19:04 / 19:05— —
19:08 / 19:09— —
19:12— —
19:15 / 19:19— —
19:22— —
19:28 / 19:29— —
19:33— —
19:36 / 19:37— —
19:39— —
19:43— —
19:48 / 19:49— —
19:55— —
20:02 / 20:03— —
20:13— —

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 20:39Partial coverage+23 min+23 min
Sat 7 NovZevenaar 20:54Partial coverage+37 min+38 min
Sun 1 NovZevenaar 20:27No data—
Sat 31 OctZevenaar 20:17No data—
Sun 25 OctZevenaar 20:20No data—
Sat 24 OctZevenaar 20:44No data—
Sun 18 OctZevenaar 20:170 min—
Sat 17 OctZevenaar 20:44No data—
Sun 11 OctZevenaar 20:27+15 min+15 min
Sat 10 OctZevenaar 20:25+7 min+7 min
Sun 4 OctZevenaar 20:39No data—
Sat 3 OctZevenaar 20:47No data—
Sun 27 SeptZevenaar 20:19No data—
Sat 26 SeptZevenaar 20:23No data—
Sun 20 SeptZevenaar 20:43No data—
Sat 19 SeptZevenaar 20:41No data—
Sun 13 SeptZevenaar 20:19No data—
Sat 12 SeptZevenaar 20:25No data—
Sun 6 SeptZevenaar 20:41No data—
Sat 5 SeptZevenaar 20:29No data—
Sun 30 AugZevenaar 20:25No data—
Sat 29 AugZevenaar 20:54No data—
Sun 23 AugZevenaar 20:38No data—
Sat 22 AugZevenaar 20:41No data—
Fri 21 AugZevenaar 20:17No data—
Sun 16 AugZevenaar 20:21No data—
Sat 15 AugZevenaar 20:28No data—
Fri 14 AugZevenaar 20:17No data—
Thu 13 AugZevenaar 20:17No data—