Train Arriva 32267 Nijmegen → Venlo

Nijmegen 18:38 → Venlo 19:31 Daily 0 h 53 min · 9 stops Arriva

Arriva 32267 Nijmegen–Venlo: final delay under 3 min on 9 of its 10 runs with data in the last 30 days (90%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 19:54 (GMT+1).

✓ Today’s run finished

Today, last fix heading to Blerick at 19:44 +4 min

  1. Nijmegen18:38
  2. Nijmegen Heyendaal18:41
  3. Cuijk18:50
  4. Boxmeer18:59
  5. Vierlingsbeek19:07
  6. Blerick19:28
  7. Venlo19:31

Next service: tomorrow 18:38 from Nijmegen · Mon 23 Nov

Next departure 18:38 tomorrow · Nijmegen
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 6 full · 4 partial · 5 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 10 full · 4 partial · 28 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 22 Nov Max en route +4 min · last fix heading to Blerick +4 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=1
  • — T n=0
  • 100% W n=1
  • — T n=0
  • 100% F n=3
  • 100% S n=4
  • 80% S n=5

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
18:38on time on time
18:41≈ on time ≈ on time
18:46≈ on time ≈ on time
18:50 / 18:52≈ on time ≈ on time
18:59 / 19:02≈ on time ≈ on time
19:07 / 19:08≈ on time ≈ on time
19:14 / 19:15≈ on time ≈ on time
19:28≈ on time ≈ +1 min
19:31on 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
Sun 22 NovBlerick 19:44Partial coverage+4 min+4 min
Sat 21 NovBlerick 19:42Partial coverage0 min—
Fri 20 NovVenray 19:29Partial coverage0 min—
Wed 18 NovNijmegen Heyendaal 18:53Partial coverage+2 min+2 min
Sun 15 NovSwalmen 20:040 min—
Sat 14 NovSwalmen 20:040 min—
Fri 13 NovCuijk 19:040 min—
Sun 8 NovSwalmen 20:04+1 min—
Sat 7 NovSwalmen 20:040 min+1 min
Fri 6 NovMook-Molenhoek 18:590 min—
Sun 1 NovSwalmen 20:04No data—
Sat 31 OctSwalmen 20:04No data—
Fri 30 OctCuijk 19:06No data—
Sun 25 OctSwalmen 20:08No data—
Sat 24 OctSwalmen 20:06No data—
Sun 18 OctSwalmen 20:06+1 min+1 min
Sat 17 OctSwalmen 20:04No data—
Fri 16 OctSwalmen 20:04No data—
Tue 13 OctNijmegen 18:50No data—
Mon 12 OctNijmegen Heyendaal 18:550 min—
Sun 11 OctSwalmen 20:050 min—
Sat 10 OctSwalmen 20:050 min—
Sun 4 OctVierlingsbeek 19:22No data—
Sat 3 OctVierlingsbeek 19:22No data—
Fri 2 OctMook-Molenhoek 19:00No data—
Sun 27 SeptSwalmen 20:05No data—
Sat 26 SeptSwalmen 20:04No data—
Sun 20 SeptBlerick 19:42No data—
Sat 19 SeptBlerick 19:44No data—
Fri 18 SeptMook-Molenhoek 19:00No data—