Train Arriva 32363 Nijmegen – Venlo

Nijmegen 17:53 → Venlo 18:53 Mon, Tue, Wed, Thu, Fri 1 h 00 min · 9 stops Arriva

It does not run today

Last recorded run: Friday 6 November +3 min

Next service: Monday 17:53 from Nijmegen · Mon 9 Nov

Next departure 17:53 Monday · Nijmegen
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 7 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 33 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: +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

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

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

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
17:53on time +1 min
17:56— —
18:02— —
18:06 / 18:07— —
18:15— —
18:21— —
18:27 / 18:32— —
18:50— —
18:53— —

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 6 NovVenray 18:44Partial coverage+3 min+3 min
Thu 5 NovCuijk 18:19No data—
Wed 4 NovBoxmeer 18:29Partial coverage0 min—
Tue 3 NovCuijk 18:19No data—
Fri 30 OctBlerick 19:04No data—
Thu 29 OctMook-Molenhoek 18:16No data—
Tue 27 OctMook-Molenhoek 18:16Partial coverage0 min—
Mon 26 OctCuijk 18:21No data—
Fri 16 OctBlerick 19:10No data—
Thu 15 OctVierlingsbeek 18:35No data—
Mon 12 OctVenray 18:46Partial coverage0 min—
Fri 9 OctVenray 18:46Partial coverage+1 min—
Thu 8 OctMook-Molenhoek 18:16Partial coverage0 min—
Wed 7 OctCuijk 18:21Partial coverage0 min—
Tue 6 OctMook-Molenhoek 18:16Partial coverage0 min—
Mon 5 OctCuijk 18:21Partial coverage0 min—
Fri 2 OctVenray 18:46No data—
Thu 1 OctMook-Molenhoek 18:16No data—
Wed 30 SeptCuijk 18:18No data—
Tue 29 SeptCuijk 18:21No data—
Mon 28 SeptMook-Molenhoek 18:16No data—
Thu 24 SeptNijmegen Heyendaal 18:11No data—
Wed 23 SeptCuijk 18:21No data—
Tue 22 SeptMook-Molenhoek 18:16No data—
Fri 18 SeptVenray 18:46No data—
Thu 17 SeptCuijk 18:21No data—
Wed 16 SeptMook-Molenhoek 18:16No data—
Tue 15 SeptCuijk 18:21No data—
Mon 14 SeptCuijk 18:21No data—
Thu 10 SeptCuijk 18:22No data—