Train Eurobahn 20073 Venlo – Hagen Hbf

Venlo 09:05 → Hagen Hbf 10:55 Daily 1 h 50 min · 17 stops Eurobahn

It has not run yet today

Last recorded run: Sunday 1 November No data

Next service: today 09:05 from Venlo · Sat 7 Nov

Next departure 09:05 today · Venlo
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 12 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
09:05on time on time
09:09 / 09:10— —
09:13 / 09:14— —
09:16 / 09:17— —
09:20 / 09:21— —
09:26 / 09:27— —
09:36 / 09:45— —
09:56 / 09:57— —
10:05 / 10:06— —
10:09 / 10:12— —
10:25 / 10:26— —
10:31 / 10:32— —
10:35 / 10:36— —
10:38 / 10:39— —
10:42 / 10:43— —
10:46 / 10:47— —
10: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
Sun 1 NovVenlo 09:20No data—
Sat 31 OctVenlo 09:20No data—
Fri 30 OctVenlo 09:24No data—
Thu 29 OctVenlo 09:21No data—
Wed 28 OctVenlo 09:21Partial coverage0 min—
Tue 27 OctVenlo 09:23Partial coverage0 min—
Mon 26 OctVenlo 09:27Partial coverage0 min—
Sun 25 OctVenlo 09:20No data—
Fri 23 OctVenlo 09:19No data—
Thu 22 OctVenlo 09:21No data—
Wed 21 OctVenlo 09:19No data—
Tue 20 OctVenlo 09:19Partial coverage0 min—
Mon 19 OctVenlo 09:21Partial coverage0 min—
Sun 18 OctVenlo 09:19Partial coverage0 min—
Sat 17 OctVenlo 09:20Partial coverage0 min—
Fri 16 OctVenlo 09:19No data—
Thu 15 OctVenlo 09:30No data—
Wed 14 OctVenlo 09:19No data—
Tue 13 OctVenlo 09:31No data—
Mon 12 OctVenlo 09:21Partial coverage0 min—
Sun 11 OctVenlo 09:22Partial coverage0 min—
Sat 10 OctVenlo 09:19Partial coverage0 min—
Fri 9 OctVenlo 09:19Partial coverage0 min—
Thu 8 OctVenlo 09:21Partial coverage0 min—
Wed 7 OctVenlo 09:19Partial coverage0 min—
Tue 6 OctVenlo 09:19Partial coverage0 min—
Mon 5 OctVenlo 09:21No data—
Fri 2 OctVenlo 09:20No data—
Thu 1 OctVenlo 09:19No data—
Wed 30 SeptVenlo 09:19No data—