Train Arriva 32233 Nijmegen → Venlo

Nijmegen 10:08 → Venlo 11:01 Daily 0 h 53 min · 9 stops Arriva

Running now · updated 11:03

Position estimated from the timetable

Heading to Venlo 0 min

Estimated arrival at Venlo 11:01

  1. Nijmegen10:08
  2. Nijmegen Heyendaal10:11
  3. Cuijk10:20
  4. Boxmeer10:29
  5. Vierlingsbeek10:37
  6. Blerick10:58
  7. Venlo11:01

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 23 runs arrived on time.

On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 19 full · 4 partial · 7 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 27 full · 4 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Venlo, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 18 Oct Max en route +5 min · last fix heading to Swalmen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 30
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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 10Today
10:08on time on time
10:11≈ on time ≈ on time
10:16≈ on time ≈ on time
10:20 / 10:22≈ on time ≈ on time
10:29 / 10:32≈ on time ≈ +1 min
10:37 / 10:38≈ on time ≈ +1 min
10:44 / 10:45≈ on time ≈ +1 min
10:58≈ on time ≈ +1 min
11:01on time +1 min

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 21 NovBlerick 10:59Partial coverage0 min—
Fri 20 NovBlerick 11:14Partial coverage+2 min+2 min
Thu 19 NovBlerick 11:13Partial coverage+2 min+2 min
Wed 18 NovBlerick 11:13Partial coverage0 min—
Tue 17 NovSwalmen 11:34+1 min+2 min
Mon 16 NovSwalmen 11:340 min+2 min
Sun 15 NovSwalmen 11:34+1 min—
Sat 14 NovSwalmen 11:340 min—
Fri 13 NovSwalmen 11:340 min—
Thu 12 NovSwalmen 11:34+1 min—
Wed 11 NovSwalmen 11:340 min—
Tue 10 NovSwalmen 11:38+3 min+3 min
Mon 9 NovSwalmen 11:340 min—
Sun 8 NovSwalmen 11:340 min—
Sat 7 NovSwalmen 11:340 min—
Fri 6 NovSwalmen 11:34No data—
Thu 5 NovSwalmen 11:34No data—
Wed 4 NovSwalmen 11:340 min—
Tue 3 NovSwalmen 11:350 min—
Mon 2 NovSwalmen 11:340 min—
Sun 1 NovSwalmen 11:36No data—
Sat 31 OctSwalmen 11:350 min—
Fri 30 OctSwalmen 11:37No data—
Thu 29 OctSwalmen 11:350 min—
Wed 28 OctSwalmen 11:360 min—
Tue 27 OctSwalmen 11:420 min—
Mon 26 OctSwalmen 11:34No data—
Sun 25 OctSwalmen 11:34No data—
Sat 24 OctSwalmen 11:36+1 min+1 min
Fri 23 OctSwalmen 11:35No data—