Train Arriva 32269 Nijmegen – Venlo

Nijmegen 19:08 → Venlo 20:01 Daily 0 h 53 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Mook-Molenhoek at 19:29 0 min

  1. Nijmegen19:08
  2. Nijmegen Heyendaal19:11
  3. Mook-Molenhoek19:16
  4. Cuijk19:20
  5. Boxmeer19:29
  6. Vierlingsbeek19:37
  7. Venlo20:01

Next service: tomorrow 19:08 from Nijmegen · Sat 21 Nov

Next departure 19:08 tomorrow · Nijmegen
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 5 full · 1 partial · 3 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 8 full · 1 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 9 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
19:08on time +1 min
19:11≈ on time ≈ +1 min
19:16≈ on time ≈ +1 min
19:20 / 19:22≈ on time ≈ +1 min
19:29 / 19:32≈ on time ≈ +1 min
19:37 / 19:38≈ on time ≈ +1 min
19:44 / 19:45≈ on time ≈ +1 min
19:58≈ on time ≈ +1 min
20: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
Fri 20 NovMook-Molenhoek 19:29Partial coverage0 min—
Sun 15 NovSwalmen 20:340 min+1 min
Sat 14 NovBlerick 20:12+1 min+1 min
Sun 8 NovSwalmen 20:340 min—
Sat 7 NovBlerick 20:120 min—
Sun 1 NovSwalmen 20:34+1 min+1 min
Sat 31 OctSwalmen 20:34No data—
Sun 25 OctSwalmen 20:34No data—
Sat 24 OctSwalmen 20:37No data—
Sun 18 OctSwalmen 20:360 min+1 min
Sat 17 OctSwalmen 20:34No data—
Fri 16 OctVenray 19:59No data—
Sun 11 OctSwalmen 20:340 min—
Sat 10 OctBlerick 20:120 min—
Sun 4 OctVierlingsbeek 19:52No data—
Sat 3 OctVierlingsbeek 19:52No data—
Sun 27 SeptSwalmen 20:35No data—
Sat 26 SeptBlerick 20:12No data—
Sun 20 SeptBlerick 20:14No data—
Sat 19 SeptBlerick 20:13No data—
Sun 13 SeptBlerick 20:15No data—
Sat 12 SeptBlerick 20:12No data—
Sun 6 SeptSwalmen 20:34No data—
Sat 5 SeptBlerick 20:14No data—
Sun 30 AugBlerick 20:12No data—
Sat 29 AugBlerick 20:12No data—
Fri 28 AugCuijk 19:36No data—
Wed 26 AugNijmegen 19:22No data—
Sun 23 AugSwalmen 20:34No data—