Train Arriva 32238 Venlo – Nijmegen

Venlo 11:59 → Nijmegen 12:52 Daily 0 h 53 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Nijmegen Heyendaal at 13:04 +2 min

  1. Venlo11:59
  2. Blerick12:01
  3. Vierlingsbeek12:20
  4. Boxmeer12:26
  5. Cuijk12:37
  6. Nijmegen Heyendaal12:48
  7. Nijmegen12:52

Next service: tomorrow 11:59 from Venlo · Thu 19 Nov

Next departure 11:59 tomorrow · Venlo
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 18 full · 1 partial · 11 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 26 full · 1 partial · 61 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 8 Oct Max en route +6 min · last fix heading to Nijmegen Heyendaal +6 min
  • Sun 15 Nov Max en route +5 min · last fix heading to Nijmegen Heyendaal +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 50% T n=2
  • 100% F n=2
  • 100% S n=5
  • 80% S n=5

Stops and timetable

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

Last 90 days, 27 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
11:59on time on time
12:01≈ on time ≈ on time
12:14 / 12:15≈ on time ≈ +1 min
12:20 / 12:21≈ on time ≈ +1 min
12:26 / 12:30≈ on time ≈ +1 min
12:37 / 12:38≈ on time ≈ +2 min
12:42≈ on time ≈ +2 min
12:48≈ +1 min ≈ +2 min
12:52+1 min +2 min

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
Wed 18 NovNijmegen Heyendaal 13:04Partial coverage+2 min+2 min
Tue 17 NovNijmegen Heyendaal 13:030 min—
Mon 16 NovNijmegen Heyendaal 13:030 min—
Sun 15 NovNijmegen Heyendaal 13:07+5 min+5 min
Sat 14 NovNijmegen Heyendaal 13:03+1 min—
Fri 13 NovNijmegen Heyendaal 13:030 min—
Thu 12 NovNijmegen Heyendaal 13:04+2 min+2 min
Wed 11 NovNijmegen Heyendaal 13:020 min—
Tue 10 NovNijmegen Heyendaal 13:03+1 min+1 min
Mon 9 NovNijmegen Heyendaal 13:03+1 min—
Sun 8 NovNijmegen Heyendaal 13:020 min—
Sat 7 NovNijmegen Heyendaal 13:03+1 min—
Fri 6 NovNijmegen Heyendaal 13:02No data—
Thu 5 NovNijmegen Heyendaal 13:03No data—
Wed 4 NovNijmegen Heyendaal 13:020 min—
Tue 3 NovNijmegen Heyendaal 12:59No data—
Mon 2 NovNijmegen Heyendaal 13:03No data—
Sun 1 NovTegelen 12:07+1 min—
Sat 31 OctTegelen 12:06+1 min+1 min
Fri 30 OctNijmegen Heyendaal 13:03No data—
Thu 29 OctNijmegen Heyendaal 13:06No data—
Wed 28 OctNijmegen Heyendaal 13:020 min—
Tue 27 OctNijmegen Heyendaal 13:020 min—
Mon 26 OctNijmegen Heyendaal 13:02No data—
Sun 25 OctTegelen 12:06No data—
Sat 24 OctTegelen 12:060 min+1 min
Fri 23 OctTegelen 12:07No data—
Thu 22 OctTegelen 12:06No data—
Wed 21 OctTegelen 12:05No data—
Tue 20 OctTegelen 12:060 min—