Train Eurobahn 20081 Venlo – 4220818

Venlo 13:05 → 4220818 15:34 Daily 2 h 29 min · 21 stops Eurobahn

It has not run yet today

Last recorded run: Sunday 1 November No data

Next service: today 13:05 from Venlo · Fri 6 Nov

Next departure 13:05 today · Venlo
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 0 full · 11 partial · 13 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 0 full · 14 partial · 63 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

  • Sat 10 Oct Max en route +5 min · last fix heading to Venlo +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
13:05on time on time
13:09 / 13:10— —
13:13 / 13:14— —
13:16 / 13:17— —
13:20 / 13:21— —
13:26 / 13:27— —
13:36 / 13:45— —
13:56 / 13:57— —
14:09 / 14:12— —
14:25 / 14:26— —
14:31 / 14:32— —
14:35 / 14:36— —
14:38 / 14:39— —
14:42 / 14:43— —
14:46 / 14:47— —
14:55 / 14:58— —
15:07 / 15:08— —
15:13 / 15:14— —
15:19 / 15:20— —
15:24 / 15:25— —
15:34— —

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
Sun 1 NovVenlo 13:20No data—
Sat 31 OctVenlo 13:20No data—
Fri 30 OctVenlo 13:33No data—
Thu 29 OctVenlo 13:20No data—
Wed 28 OctVenlo 13:25Partial coverage0 min—
Tue 27 OctVenlo 13:28Partial coverage0 min—
Mon 26 OctVenlo 13:19Partial coverage0 min—
Sun 25 OctVenlo 13:48No data—
Fri 23 OctVenlo 13:22No data—
Thu 22 OctVenlo 13:28No data—
Wed 21 OctVenlo 13:19No data—
Tue 20 OctVenlo 13:23Partial coverage0 min—
Mon 19 OctVenlo 13:20Partial coverage0 min—
Sun 18 OctVenlo 13:20Partial coverage0 min—
Sat 17 OctVenlo 13:19No data—
Fri 16 OctVenlo 13:30No data—
Thu 15 OctVenlo 13:20No data—
Wed 14 OctVenlo 13:19No data—
Tue 13 OctVenlo 13:19No data—
Mon 12 OctVenlo 13:28Partial coverage0 min—
Sun 11 OctVenlo 13:20Partial coverage0 min—
Sat 10 OctVenlo 13:40Partial coverage+5 min+5 min
Fri 9 OctVenlo 13:19Partial coverage0 min—
Thu 8 OctVenlo 13:19Partial coverage0 min—
Wed 7 OctVenlo 13:30Partial coverage0 min—
Tue 6 OctVenlo 13:19Partial coverage0 min—
Mon 5 OctVenlo 13:19Partial coverage0 min—
Fri 2 OctVenlo 13:19No data—
Thu 1 OctVenlo 13:19No data—
Wed 30 SeptVenlo 13:21No data—