Train Eurobahn 20069 Venlo – Hamm (Westf.)

Venlo 07:05 → Hamm (Westf.) 09:34 Daily 2 h 29 min · 22 stops Eurobahn

✓ Today’s run finished

Today, last fix heading to Venlo at 07:23 0 min

  1. Venlo07:05
  2. Kaldenkirchen07:09
  3. Dülken07:20
  4. Neuss Hbf07:56
  5. Wuppertal Hbf08:31
  6. Schwelm08:42
  7. Hamm (Westf.)09:34

Next service: tomorrow 07:05 from Venlo · Sun 8 Nov

Next departure 07:05 tomorrow · Venlo
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 20 full · 1 partial · 3 no data
On-time · 90 days
92%
22/24 runs under 3 min
RT coverage: 23 full · 1 partial · 53 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 Hamm (Westf.), in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 30 Oct Max en route +5 min · last fix heading to Venlo +5 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Venlo +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 22
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
07:05on time on time
07:09 / 07:10≈ on time ≈ on time
07:13 / 07:14≈ on time ≈ on time
07:16 / 07:17≈ on time ≈ on time
07:20 / 07:21≈ on time ≈ on time
07:26 / 07:27≈ on time ≈ on time
07:36 / 07:45≈ on time ≈ on time
07:56 / 07:57≈ on time ≈ on time
08:05 / 08:06≈ on time ≈ on time
08:10 / 08:12≈ on time ≈ on time
08:25 / 08:26≈ on time ≈ on time
08:31 / 08:32≈ on time ≈ on time
08:35 / 08:36≈ on time ≈ on time
08:38 / 08:39≈ on time ≈ on time
08:42 / 08:43≈ on time ≈ on time
08:46 / 08:47≈ on time ≈ on time
08:55 / 08:58≈ on time ≈ on time
09:07 / 09:08≈ on time ≈ on time
09:13 / 09:14≈ on time ≈ on time
09:19 / 09:20≈ on time ≈ on time
09:24 / 09:25≈ on time ≈ on time
09:34on time on time

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 7 NovVenlo 07:23Partial coverage0 min—
Sun 1 NovVenlo 07:19No data—
Sat 31 OctVenlo 07:20No data—
Fri 30 OctVenlo 07:41+5 min+5 min
Thu 29 OctVenlo 07:190 min—
Wed 28 OctVenlo 07:230 min—
Tue 27 OctVenlo 07:260 min—
Mon 26 OctVenlo 07:190 min—
Sun 25 OctVenlo 07:22No data—
Fri 23 OctVenlo 07:260 min—
Thu 22 OctVenlo 07:190 min—
Wed 21 OctVenlo 07:220 min—
Tue 20 OctVenlo 07:190 min—
Mon 19 OctVenlo 07:200 min—
Sun 18 OctVenlo 07:190 min—
Sat 17 OctVenlo 07:190 min—
Fri 16 OctVenlo 07:190 min—
Thu 15 OctVenlo 07:220 min—
Wed 14 OctVenlo 07:190 min—
Tue 13 OctVenlo 07:240 min—
Mon 12 OctVenlo 07:210 min—
Sun 11 OctVenlo 07:40+5 min+5 min
Sat 10 OctVenlo 07:190 min—
Fri 9 OctVenlo 07:190 min—
Thu 8 OctVenlo 07:200 min—
Wed 7 OctVenlo 07:190 min—
Tue 6 OctVenlo 07:190 min—
Mon 5 OctVenlo 07:22No data—
Fri 2 OctVenlo 07:19No data—
Thu 1 OctVenlo 07:22No data—