Train Arriva 32318 Venlo – Nijmegen

Venlo 07:12 → Nijmegen 08:07 Mon, Tue, Wed, Thu, Fri 0 h 55 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Nijmegen Heyendaal at 08:18 No data

  1. Venlo07:12
  2. Blerick07:15
  3. Vierlingsbeek07:38
  4. Boxmeer07:44
  5. Cuijk07:52
  6. Nijmegen Heyendaal08:03
  7. Nijmegen08:07

Next service: Monday 07:12 from Venlo · Mon 9 Nov

Next departure 07:12 Monday · Venlo
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 0 full · 8 partial · 7 no data
On-time · 90 days
80%
8/10 runs under 3 min
RT coverage: 0 full · 10 partial · 37 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +1 min

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

Worst days

  • Wed 7 Oct Max en route +6 min · last fix heading to Nijmegen Heyendaal +6 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Nijmegen Heyendaal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 8
  • 3–10 min 20% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=2
  • 67% W n=3
  • 67% T n=3
  • 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, 10 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
07:12on time +1 min
07:15— —
07:32 / 07:33— —
07:38 / 07:39— —
07:44 / 07:45— —
07:52 / 07:53— —
07:57— —
08:03— —
08:07— —

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 NovNijmegen Heyendaal 08:18No data—
Thu 5 NovNijmegen Heyendaal 08:19No data—
Wed 4 NovNijmegen Heyendaal 08:18Partial coverage+1 min—
Tue 3 NovNijmegen Heyendaal 08:19No data—
Mon 2 NovNijmegen Heyendaal 08:18No data—
Fri 30 OctNijmegen Heyendaal 08:18No data—
Thu 29 OctNijmegen Heyendaal 08:17Partial coverage0 min—
Wed 28 OctNijmegen Heyendaal 08:17Partial coverage0 min—
Tue 27 OctNijmegen Heyendaal 08:17Partial coverage0 min—
Mon 26 OctNijmegen Heyendaal 08:17Partial coverageNo data—
Fri 16 OctNijmegen Heyendaal 08:17Partial coverage0 min—
Thu 15 OctNijmegen Heyendaal 08:19Partial coverage0 min—
Mon 12 OctNijmegen Heyendaal 08:17No data—
Fri 9 OctNijmegen Heyendaal 08:17Partial coverage0 min+1 min
Thu 8 OctNijmegen Heyendaal 08:21Partial coverage+4 min+4 min
Wed 7 OctNijmegen Heyendaal 08:23Partial coverage+6 min+6 min
Tue 6 OctNijmegen Heyendaal 08:17Partial coverage0 min—
Mon 5 OctNijmegen Heyendaal 08:20No data—
Fri 2 OctNijmegen Heyendaal 08:32No data—
Thu 1 OctNijmegen Heyendaal 08:17No data—
Wed 30 SeptNijmegen Heyendaal 08:17No data—
Tue 29 SeptNijmegen Heyendaal 08:18No data—
Mon 28 SeptNijmegen Heyendaal 08:17No data—
Fri 25 SeptNijmegen Heyendaal 08:17No data—
Thu 24 SeptNijmegen Heyendaal 08:17No data—
Wed 23 SeptNijmegen Heyendaal 08:19No data—
Tue 22 SeptNijmegen Heyendaal 08:17No data—
Mon 21 SeptNijmegen Heyendaal 08:17No data—
Fri 18 SeptNijmegen Heyendaal 08:18No data—
Thu 17 SeptNijmegen Heyendaal 08:18No data—