Train VIAS 20041 Arnhem Centraal – Duisburg Hbf

Arnhem Centraal 21:45 → Duisburg Hbf 23:15 Mon, Tue, Wed, Thu, Sat, Sun 1 h 30 min · 18 stops VIAS

It does not run today

Last recorded run: Sunday 8 November 0 min

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

Next departure 21:45 Monday · Arnhem Centraal
On-time · 30 days
67%
2/3 runs under 3 min
RT coverage: 1 full · 2 partial · 5 no data
On-time · 90 days
80%
4/5 runs under 3 min
RT coverage: 3 full · 2 partial · 19 no data
Typical delay
0min
Median at arrival, 90 days
P90
+7min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Duisburg 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 7 Nov Max en route +12 min · last fix heading to Zevenaar +12 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 80% · 4
  • 3–10 min 0% · 0
  • 10–30 min 20% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (18 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
21:45on time +1 min
21:54— —
22:00— —
22:06 / 22:08— —
22:12— —
22:16— —
22:18 / 22:19— —
22:22— —
22:26 / 22:27— —
22:33— —
22:37 / 22:43— —
22:46 / 22:47— —
22:50 / 22:51— —
22:54 / 22:55— —
22:59 / 23:00— —
23:02 / 23:03— —
23:07 / 23:08— —
23:15— —

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 22:09Partial coverage0 min—
Sat 7 NovZevenaar 22:19Partial coverage+12 min+12 min
Sun 1 NovZevenaar 22:24No data—
Sat 31 OctZevenaar 22:11No data—
Sun 25 OctZevenaar 22:08No data—
Sat 24 OctZevenaar 22:08No data—
Sun 18 OctZevenaar 22:110 min—
Sat 17 OctZevenaar 22:08No data—
Sun 11 OctZevenaar 22:140 min+1 min
Sat 10 OctZevenaar 22:080 min—
Sun 27 SeptZevenaar 22:09No data—
Sat 26 SeptZevenaar 22:08No data—
Sun 20 SeptZevenaar 22:09No data—
Sat 19 SeptZevenaar 22:08No data—
Sun 13 SeptZevenaar 22:08No data—
Sat 12 SeptZevenaar 22:08No data—
Sun 6 SeptZevenaar 22:11No data—
Sat 5 SeptZevenaar 22:08No data—
Sun 30 AugZevenaar 22:12No data—
Sat 29 AugZevenaar 22:08No data—
Sun 23 AugZevenaar 22:13No data—
Sat 22 AugZevenaar 22:10No data—
Sun 16 AugZevenaar 22:28No data—
Sat 15 AugZevenaar 22:10No data—