Train Eurobahn 20065 Venlo – Hagen Hbf

Venlo 05:05 → Hagen Hbf 06:55 Mon, Tue, Wed, Thu, Fri, Sat 1 h 50 min · 17 stops Eurobahn

It has not run yet today

Last recorded run: Saturday 31 October No data

Next service: tomorrow 05:05 from Venlo · Sat 7 Nov

Next departure 05:05 tomorrow · Venlo
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 1 full · 16 partial · 3 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 1 full · 18 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Hagen 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

  • Tue 6 Oct Max en route +43 min · last fix heading to Venlo +43 min
  • Wed 28 Oct Max en route +13 min · last fix heading to Venlo +13 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 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 5% · 1

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (17 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
Venlo
05:05on time on time
Kaldenkirchen
05:09 / 05:10— —
Breyell
05:13 / 05:14— —
Boisheim
05:16 / 05:17— —
Dülken
05:20 / 05:21— —
Viersen
05:26 / 05:27— —
Mönchengladbach Hbf
05:36 / 05:45— —
Neuss Hbf
05:56 / 05:57— —
4220849
06:05 / 06:06— —
Düsseldorf Hbf
06:09 / 06:12— —
Wuppertal-Vohwinkel
06:25 / 06:26— —
Wuppertal Hbf
06:31 / 06:32— —
Wuppertal-Barmen
06:35 / 06:36— —
Wuppertal-Oberbarmen
06:38 / 06:39— —
Schwelm
06:42 / 06:43— —
Ennepetal
06:46 / 06:47— —
Hagen Hbf
06:55— —

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 31 OctVenlo 05:21No data—
Fri 30 OctVenlo 05:20Partial coverage0 min—
Thu 29 OctVenlo 05:19No data—
Wed 28 OctVenlo 05:55Partial coverage+13 min+13 min
Tue 27 OctVenlo 05:19Partial coverage0 min—
Mon 26 OctVenlo 05:20Partial coverage0 min—
Sat 24 OctVenlo 05:20Partial coverage0 min—
Thu 22 OctVenlo 05:22Partial coverage0 min—
Wed 21 OctVenlo 05:19Partial coverage0 min—
Tue 20 OctVenlo 05:19Partial coverage0 min—
Mon 19 OctVenlo 05:19Partial coverage0 min—
Sat 17 OctVenlo 05:19Partial coverage0 min—
Fri 16 OctVenlo 05:19Partial coverage0 min—
Thu 15 OctVenlo 05:19Partial coverage0 min—
Wed 14 OctVenlo 05:19Partial coverage0 min—
Tue 13 OctVenlo 05:32Partial coverage0 min—
Mon 12 OctVenlo 05:19Partial coverage0 min—
Sat 10 OctVenlo 05:190 min—
Fri 9 OctVenlo 05:19Partial coverage0 min—
Thu 8 OctVenlo 05:19Partial coverageNo data—
Wed 7 OctVenlo 05:34Partial coverage0 min—
Tue 6 OctVenlo 06:19Partial coverage+43 min+43 min
Fri 2 OctVenlo 05:19No data—
Thu 1 OctVenlo 05:21No data—
Wed 30 SeptVenlo 05:19No data—
Tue 29 SeptVenlo 05:26No data—
Mon 28 SeptVenlo 05:22No data—
Sat 26 SeptVenlo 05:30No data—
Thu 24 SeptVenlo 05:19No data—
Wed 23 SeptVenlo 05:20No data—