Train Eurobahn 20083 Venlo – Hamm (Westf.)

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

✓ Today’s run finished

Today, last fix heading to Venlo at 14:19 0 min

  1. Venlo14:05
  2. Kaldenkirchen14:09
  3. Dülken14:20
  4. Neuss Hbf14:56
  5. Wuppertal Hbf15:31
  6. Schwelm15:42
  7. Hamm (Westf.)16:34

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

Next departure 14:05 tomorrow · Venlo
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 11 full · 1 partial · 9 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 15 full · 1 partial · 58 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 16
  • 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=2
  • 100% F n=1
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

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