Train Arriva 32344 Venray – Nijmegen

Venray 14:03 → Nijmegen 14:37 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 7 stops Arriva

✓ Today’s run finished

Today, last fix heading to Nijmegen Heyendaal at 14:47 No data

  1. Venray14:03
  2. Vierlingsbeek14:08
  3. Boxmeer14:14
  4. Cuijk14:22
  5. Mook-Molenhoek14:27
  6. Nijmegen Heyendaal14:33
  7. Nijmegen14:37

Next service: tomorrow 14:03 from Venray · Wed 11 Nov

Next departure 14:03 tomorrow · Venray
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 0 full · 3 partial · 12 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 0 full · 6 partial · 42 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Nijmegen, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 6 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
14:03on time on time
14:08 / 14:09— —
14:14 / 14:15— —
14:22 / 14:23— —
14:27— —
14:33— —
14:37— —

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
Tue 10 NovNijmegen Heyendaal 14:47No data—
Mon 9 NovNijmegen Heyendaal 14:44No data—
Fri 6 NovMook-Molenhoek 14:39No data—
Thu 5 NovNijmegen Heyendaal 14:47No data—
Wed 4 NovNijmegen Heyendaal 14:47Partial coverage0 min—
Tue 3 NovNijmegen Heyendaal 14:47No data—
Mon 2 NovNijmegen Heyendaal 14:49No data—
Fri 30 OctNijmegen Heyendaal 14:47No data—
Thu 29 OctNijmegen Heyendaal 14:47No data—
Wed 28 OctNijmegen Heyendaal 15:05Partial coverage0 min—
Tue 27 OctNijmegen Heyendaal 14:47Partial coverage0 min—
Mon 26 OctNijmegen Heyendaal 14:47No data—
Fri 16 OctNijmegen Heyendaal 14:53No data—
Thu 15 OctNijmegen Heyendaal 14:47No data—
Mon 12 OctNijmegen Heyendaal 14:47No data—
Fri 9 OctNijmegen Heyendaal 14:47Partial coverage0 min—
Thu 8 OctNijmegen Heyendaal 14:47No data—
Wed 7 OctNijmegen Heyendaal 14:47Partial coverage0 min—
Tue 6 OctNijmegen Heyendaal 14:47No data—
Mon 5 OctNijmegen Heyendaal 14:47Partial coverage0 min—
Fri 2 OctNijmegen Heyendaal 14:50No data—
Thu 1 OctNijmegen Heyendaal 14:48No data—
Wed 30 SeptNijmegen Heyendaal 14:47No data—
Tue 29 SeptNijmegen Heyendaal 14:48No data—
Mon 28 SeptNijmegen Heyendaal 14:47No data—
Fri 25 SeptNijmegen Heyendaal 14:47No data—
Wed 23 SeptNijmegen Heyendaal 14:47No data—
Tue 22 SeptNijmegen Heyendaal 14:49No data—
Mon 21 SeptNijmegen Heyendaal 14:47No data—
Fri 18 SeptNijmegen Heyendaal 14:47No data—