Train Eurobahn 20073 Venlo – 4220818

Venlo 09:05 → 4220818 11:34 Daily 2 h 29 min · 22 stops Eurobahn

✓ Today’s run finished

Today, last fix heading to Venlo at 09:44 +1 min

  1. Venlo09:05
  2. Kaldenkirchen09:09
  3. Dülken09:20
  4. Neuss Hbf09:56
  5. Wuppertal Hbf10:31
  6. Schwelm10:42
  7. 422081811:34

Next service: tomorrow 09:05 from Venlo · Tue 17 Nov

Next departure 09:05 tomorrow · Venlo
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 6 full · 10 partial · 8 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 14 full · 10 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: +1 min

Last 30 days

Arrival delay at 4220818, 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 13 Nov Max en route +12 min · last fix heading to Venlo +12 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 96% · 23
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

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
09:05on time on time
09:09 / 09:10≈ on time ≈ on time
09:13 / 09:14≈ on time ≈ on time
09:16 / 09:17≈ on time ≈ on time
09:20 / 09:21≈ on time ≈ on time
09:26 / 09:27≈ on time ≈ on time
09:36 / 09:45≈ on time ≈ on time
09:56 / 09:57≈ on time ≈ on time
10:05 / 10:06≈ on time ≈ on time
10:09 / 10:12≈ on time ≈ on time
10:25 / 10:26≈ on time ≈ on time
10:31 / 10:32≈ on time ≈ on time
10:35 / 10:36≈ on time ≈ on time
10:38 / 10:39≈ on time ≈ on time
10:42 / 10:43≈ on time ≈ on time
10:46 / 10:47≈ on time ≈ on time
10:55 / 10:58≈ on time ≈ on time
11:07 / 11:08≈ on time ≈ on time
11:13 / 11:14≈ on time ≈ on time
11:19 / 11:20≈ on time ≈ on time
11:24 / 11:25≈ on time ≈ on time
11: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
Mon 16 NovVenlo 09:44Partial coverage+1 min+7 min
Sun 15 NovVenlo 09:19Partial coverage0 min—
Sat 14 NovVenlo 09:54Partial coverage0 min+17 min
Fri 13 NovVenlo 09:43Partial coverage+12 min+12 min
Thu 12 NovVenlo 09:19Partial coverage0 min—
Wed 11 NovVenlo 09:24Partial coverage0 min—
Tue 10 NovVenlo 09:19Partial coverage0 min—
Mon 9 NovVenlo 09:27Partial coverage0 min—
Sun 8 NovVenlo 09:19Partial coverage0 min—
Sat 7 NovVenlo 09:19Partial coverage0 min—
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:210 min—
Tue 27 OctVenlo 09:230 min—
Mon 26 OctVenlo 09:270 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:190 min—
Mon 19 OctVenlo 09:210 min—
Sun 18 OctVenlo 09:190 min—
Sat 17 OctVenlo 09:200 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:210 min—