Train Eurobahn 20093 Venlo – Hagen Hbf

Venlo 19:05 → Hagen Hbf 20:55 Daily 1 h 50 min · 16 stops Eurobahn

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: tomorrow 19:05 from Venlo · Tue 10 Nov

Next departure 19:05 tomorrow · Venlo
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 5 full · 1 partial · 3 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 6 full · 1 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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

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

On-time by weekday

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

Stops and timetable

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

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