Train Arriva 32212 Venlo – Nijmegen

Venlo 05:29 → Nijmegen 06:22 Mon, Tue, Wed, Thu, Fri 0 h 53 min · 9 stops Arriva

Running now · updated 05:58

Heading to Nijmegen No data

Estimated arrival at Nijmegen 06:22 · 46 km/h

  1. Venlo05:29
  2. Blerick05:31
  3. Vierlingsbeek05:50
  4. Boxmeer05:56
  5. Cuijk06:07
  6. Nijmegen Heyendaal06:18
  7. Nijmegen06:22
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 1 full · 12 partial · 3 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 1 full · 13 partial · 43 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: +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

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 100% · 14
  • 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=4
  • 100% W n=3
  • 100% T n=2
  • 100% F n=3
  • — S n=0
  • — S n=0

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 10Today
05:29on time on time
05:31— —
05:44 / 05:45— —
05:50 / 05:51— —
05:56 / 06:00— —
06:07 / 06:08— —
06:12— —
06:18— —
06:22— —

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
Thu 5 NovBoxmeer 05:54No data—
Wed 4 NovNijmegen Heyendaal 06:32Partial coverage0 min—
Tue 3 NovNijmegen Heyendaal 06:320 min—
Mon 2 NovNijmegen Heyendaal 06:32No data—
Fri 30 OctNijmegen Heyendaal 06:32Partial coverage0 min—
Thu 29 OctNijmegen Heyendaal 06:33Partial coverage0 min—
Wed 28 OctNijmegen Heyendaal 06:32Partial coverage0 min—
Tue 27 OctNijmegen Heyendaal 06:32Partial coverage0 min—
Mon 26 OctNijmegen Heyendaal 06:32Partial coverage0 min—
Fri 16 OctNijmegen Heyendaal 06:32Partial coverage0 min—
Thu 15 OctNijmegen Heyendaal 06:32Partial coverage0 min—
Tue 13 OctNijmegen Heyendaal 06:33Partial coverage+1 min—
Mon 12 OctNijmegen Heyendaal 06:34Partial coverage+1 min+1 min
Fri 9 OctNijmegen Heyendaal 06:32Partial coverage0 min—
Thu 8 OctNijmegen Heyendaal 06:33No data—
Wed 7 OctNijmegen Heyendaal 06:33Partial coverage+1 min—
Tue 6 OctNijmegen Heyendaal 06:32Partial coverage0 min—
Mon 5 OctNijmegen Heyendaal 06:33No data—
Fri 2 OctNijmegen Heyendaal 06:32No data—
Thu 1 OctNijmegen Heyendaal 06:32No data—
Wed 30 SeptNijmegen Heyendaal 06:32No data—
Tue 29 SeptNijmegen Heyendaal 06:32No data—
Mon 28 SeptNijmegen Heyendaal 06:32No data—
Fri 25 SeptNijmegen Heyendaal 06:32No data—
Thu 24 SeptNijmegen Heyendaal 06:32No data—
Wed 23 SeptNijmegen Heyendaal 06:32No data—
Tue 22 SeptNijmegen Heyendaal 06:33No data—
Mon 21 SeptNijmegen Heyendaal 06:32No data—
Fri 18 SeptNijmegen Heyendaal 06:32No data—
Thu 17 SeptNijmegen Heyendaal 06:36No data—