Train Arriva 32349 Nijmegen – Venray

Nijmegen 14:23 → Venray 14:58 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 7 stops Arriva

✓ Today’s run finished

Today, last fix heading to Vierlingsbeek at 15:10 +5 min

  1. Nijmegen14:23
  2. Nijmegen Heyendaal14:26
  3. Mook-Molenhoek14:32
  4. Cuijk14:36
  5. Boxmeer14:45
  6. Vierlingsbeek14:51
  7. Venray14:58

Next service: tomorrow 14:23 from Nijmegen · Tue 17 Nov

Next departure 14:23 tomorrow · Nijmegen
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 0 full · 8 partial · 7 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 0 full · 12 partial · 38 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

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

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

Worst days

  • Mon 16 Nov Max en route +5 min · last fix heading to Vierlingsbeek +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 11
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 12 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:23on time on time
14:26— —
14:32— —
14:36 / 14:37— —
14:45— —
14:51— —
14:58— —

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
Mon 16 NovVierlingsbeek 15:10Partial coverage+5 min+5 min
Fri 13 NovVierlingsbeek 15:07Partial coverage+1 min+1 min
Wed 11 NovVierlingsbeek 15:09Partial coverage+3 min+3 min
Tue 10 NovVierlingsbeek 15:08Partial coverage+2 min+3 min
Mon 9 NovVierlingsbeek 15:04Partial coverageNo data—
Fri 6 NovVierlingsbeek 15:04No data—
Thu 5 NovVierlingsbeek 15:04No data—
Wed 4 NovVierlingsbeek 15:07Partial coverage+1 min+1 min
Tue 3 NovVierlingsbeek 15:04No data—
Mon 2 NovVierlingsbeek 15:04No data—
Fri 30 OctVierlingsbeek 15:05No data—
Thu 29 OctVierlingsbeek 15:05Partial coverage0 min—
Wed 28 OctVierlingsbeek 15:10Partial coverage0 min—
Tue 27 OctVierlingsbeek 15:11Partial coverage0 min—
Mon 26 OctVierlingsbeek 15:05No data—
Fri 16 OctVierlingsbeek 15:17No data—
Thu 15 OctVierlingsbeek 15:05No data—
Mon 12 OctVierlingsbeek 15:05No data—
Fri 9 OctVierlingsbeek 15:07Partial coverage+1 min+1 min
Thu 8 OctVierlingsbeek 15:08Partial coverage+1 min+2 min
Wed 7 OctVierlingsbeek 15:05No data—
Tue 6 OctVierlingsbeek 15:06Partial coverage+1 min—
Mon 5 OctVierlingsbeek 15:06Partial coverage0 min—
Fri 2 OctVierlingsbeek 15:10No data—
Thu 1 OctVierlingsbeek 15:06No data—
Wed 30 SeptVierlingsbeek 15:06No data—
Tue 29 SeptVierlingsbeek 15:06No data—
Mon 28 SeptVierlingsbeek 15:07No data—
Fri 25 SeptVierlingsbeek 15:06No data—
Thu 24 SeptVierlingsbeek 15:06No data—