Train Eurobahn 20071 Venlo – 4220818

Venlo 08:05 → 4220818 10:34 Daily 2 h 29 min · 22 stops Eurobahn

✓ Today’s run finished

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

  1. Venlo08:05
  2. Kaldenkirchen08:09
  3. Dülken08:20
  4. Neuss Hbf08:56
  5. Wuppertal Hbf09:31
  6. Schwelm09:42
  7. 422081810:34

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

Next departure 08:05 tomorrow · Venlo
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 8 full · 10 partial · 5 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 16 full · 10 partial · 50 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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