Train Eurobahn 20067 Venlo – 4220818

Venlo 06:05 → 4220818 08:34 Mon, Tue, Wed, Thu, Fri, Sat 2 h 29 min · 22 stops Eurobahn

✓ Today’s run finished

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

  1. Venlo06:05
  2. Kaldenkirchen06:09
  3. Dülken06:20
  4. Neuss Hbf06:56
  5. Wuppertal Hbf07:31
  6. Schwelm07:42
  7. 422081808:34

Next service: Monday 06:05 from Venlo · Mon 16 Nov

Next departure 06:05 Monday · Venlo
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 13 full · 6 partial · 0 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 21 full · 6 partial · 39 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 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 23 Oct Max en route +17 min · last fix heading to Venlo +17 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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