Train Eurobahn 20087 Venlo – 4220818

Venlo 16:05 → 4220818 18:34 Daily 2 h 29 min · 22 stops Eurobahn

✓ Today’s run finished

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

  1. Venlo16:05
  2. Kaldenkirchen16:09
  3. Dülken16:20
  4. Neuss Hbf16:56
  5. Wuppertal Hbf17:31
  6. Schwelm17:42
  7. 422081818:34

Next service: tomorrow 16:05 from Venlo · Tue 10 Nov

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

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

  • Early 0% · 0
  • On time 100% · 17
  • 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=3
  • 100% W n=2
  • 100% T n=1
  • 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, 17 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
16:05on time on time
16:09 / 16:10≈ on time ≈ on time
16:13 / 16:14≈ on time ≈ on time
16:16 / 16:17≈ on time ≈ on time
16:20 / 16:21≈ on time ≈ on time
16:26 / 16:27≈ on time ≈ on time
16:36 / 16:45≈ on time ≈ on time
16:56 / 16:57≈ on time ≈ on time
17:05 / 17:06≈ on time ≈ on time
17:09 / 17:12≈ on time ≈ on time
17:25 / 17:26≈ on time ≈ on time
17:31 / 17:32≈ on time ≈ on time
17:35 / 17:36≈ on time ≈ on time
17:38 / 17:39≈ on time ≈ on time
17:42 / 17:43≈ on time ≈ on time
17:46 / 17:47≈ on time ≈ on time
17:55 / 17:58≈ on time ≈ on time
18:07 / 18:08≈ on time ≈ on time
18:13 / 18:14≈ on time ≈ on time
18:19 / 18:20≈ on time ≈ on time
18:24 / 18:25≈ on time ≈ on time
18: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 9 NovVenlo 16:19Partial coverage0 min—
Sun 8 NovVenlo 16:20Partial coverage0 min—
Sat 7 NovVenlo 16:19Partial coverage0 min—
Sun 1 NovVenlo 16:20No data—
Sat 31 OctVenlo 16:24No data—
Thu 29 OctVenlo 16:19No data—
Wed 28 OctVenlo 16:300 min—
Tue 27 OctVenlo 16:230 min—
Mon 26 OctVenlo 16:190 min—
Sat 24 OctVenlo 16:360 min—
Fri 23 OctVenlo 16:45No data—
Thu 22 OctVenlo 17:19No data—
Wed 21 OctVenlo 16:34No data—
Tue 20 OctVenlo 16:190 min—
Mon 19 OctVenlo 16:260 min—
Sun 18 OctVenlo 16:200 min—
Sat 17 OctVenlo 16:23No data—
Fri 16 OctVenlo 16:28No data—
Wed 14 OctVenlo 16:19No data—
Tue 13 OctVenlo 16:37No data—
Mon 12 OctVenlo 16:190 min—
Sat 10 OctVenlo 16:210 min—
Fri 9 OctVenlo 16:300 min—
Thu 8 OctVenlo 16:210 min—
Wed 7 OctVenlo 16:230 min—
Tue 6 OctVenlo 16:190 min—
Mon 5 OctVenlo 16:320 min—
Fri 2 OctVenlo 16:21No data—
Thu 1 OctVenlo 16:19No data—
Wed 30 SeptVenlo 16:20No data—