Train Arriva 32214 Venlo – Nijmegen

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

✓ Today’s run finished

Today, last fix heading to Nijmegen Heyendaal at 07:03 No data

  1. Venlo05:59
  2. Blerick06:01
  3. Vierlingsbeek06:20
  4. Boxmeer06:26
  5. Cuijk06:37
  6. Nijmegen Heyendaal06:48
  7. Nijmegen06:52

Next service: tomorrow 05:59 from Venlo · Sat 7 Nov

Next departure 05:59 tomorrow · Venlo
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 0 full · 16 partial · 1 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 0 full · 18 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
05:59on time on time
06:01— —
06:14 / 06:15— —
06:20 / 06:21— —
06:26 / 06:30— —
06:37 / 06:38— —
06:42— —
06:48— —
06:52— —

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 07:03No data—
Thu 5 NovNijmegen Heyendaal 07:04Partial coverage0 min—
Wed 4 NovNijmegen Heyendaal 07:03Partial coverage+1 min—
Tue 3 NovNijmegen Heyendaal 07:02Partial coverage0 min—
Mon 2 NovNijmegen Heyendaal 07:02Partial coverage0 min—
Fri 30 OctNijmegen Heyendaal 07:03Partial coverage0 min—
Thu 29 OctNijmegen Heyendaal 07:02Partial coverage0 min—
Wed 28 OctNijmegen Heyendaal 07:02Partial coverage0 min—
Tue 27 OctNijmegen Heyendaal 07:04Partial coverage+1 min+1 min
Mon 26 OctNijmegen Heyendaal 07:04Partial coverage+2 min+2 min
Fri 16 OctNijmegen Heyendaal 07:02Partial coverage0 min—
Thu 15 OctNijmegen Heyendaal 07:03Partial coverage+1 min—
Tue 13 OctNijmegen Heyendaal 07:03Partial coverage0 min—
Mon 12 OctNijmegen Heyendaal 07:04Partial coverage0 min—
Sat 10 OctNijmegen Heyendaal 07:02Partial coverage0 min—
Fri 9 OctNijmegen Heyendaal 07:03Partial coverage+1 min—
Thu 8 OctNijmegen Heyendaal 07:02Partial coverage0 min—
Wed 7 OctNijmegen Heyendaal 07:03Partial coverage+1 min—
Tue 6 OctNijmegen Heyendaal 07:04Partial coverage+2 min+2 min
Mon 5 OctNijmegen Heyendaal 07:04No data—
Sat 3 OctNijmegen Heyendaal 07:04No data—
Fri 2 OctNijmegen Heyendaal 07:02No data—
Thu 1 OctNijmegen Heyendaal 07:02No data—
Wed 30 SeptNijmegen Heyendaal 07:02No data—
Tue 29 SeptNijmegen Heyendaal 07:02No data—
Mon 28 SeptNijmegen Heyendaal 07:03No data—
Sat 26 SeptNijmegen Heyendaal 07:02No data—
Fri 25 SeptNijmegen Heyendaal 07:02No data—
Thu 24 SeptNijmegen Heyendaal 07:02No data—
Wed 23 SeptNijmegen Heyendaal 07:03No data—