Train Arriva 32236 Venlo – Nijmegen

Venlo 11:29 → Nijmegen 12:22 Daily 0 h 53 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Nijmegen Heyendaal at 12:33 0 min

  1. Venlo11:29
  2. Blerick11:31
  3. Vierlingsbeek11:50
  4. Boxmeer11:56
  5. Cuijk12:07
  6. Nijmegen Heyendaal12:18
  7. Nijmegen12:22

Next service: tomorrow 11:29 from Venlo · Sat 21 Nov

Next departure 11:29 tomorrow · Venlo
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 17 full · 3 partial · 10 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 26 full · 3 partial · 59 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 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

Worst days

  • Sun 18 Oct Max en route +6 min · last fix heading to Tegelen +6 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Nijmegen Heyendaal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 27
  • 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
  • 100% T n=3
  • 100% F n=3
  • 100% S n=5
  • 60% S n=5

Stops and timetable

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

Last 90 days, 29 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:29on time on time
11:31≈ on time ≈ on time
11:44 / 11:45≈ on time ≈ +1 min
11:50 / 11:51≈ on time ≈ +1 min
11:56 / 12:00≈ on time ≈ +1 min
12:07 / 12:08≈ on time ≈ +1 min
12:12≈ on time ≈ +1 min
12:18≈ on time ≈ +2 min
12:22on time +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
Fri 20 NovNijmegen Heyendaal 12:33Partial coverage0 min—
Thu 19 NovNijmegen Heyendaal 12:33Partial coverage+1 min—
Wed 18 NovNijmegen Heyendaal 12:33Partial coverage+1 min—
Tue 17 NovNijmegen Heyendaal 12:33+1 min—
Mon 16 NovNijmegen Heyendaal 12:330 min—
Sun 15 NovNijmegen Heyendaal 12:35+4 min+4 min
Sat 14 NovNijmegen Heyendaal 12:320 min—
Fri 13 NovNijmegen Heyendaal 12:320 min—
Thu 12 NovNijmegen Heyendaal 12:32+1 min+1 min
Wed 11 NovNijmegen Heyendaal 12:320 min—
Tue 10 NovNijmegen Heyendaal 12:33+1 min—
Mon 9 NovNijmegen Heyendaal 12:330 min—
Sun 8 NovNijmegen Heyendaal 12:34+3 min+3 min
Sat 7 NovNijmegen Heyendaal 12:33+1 min—
Fri 6 NovNijmegen Heyendaal 12:32No data—
Thu 5 NovNijmegen Heyendaal 12:32No data—
Wed 4 NovNijmegen Heyendaal 12:320 min—
Tue 3 NovNijmegen Heyendaal 12:33No data—
Mon 2 NovNijmegen Heyendaal 12:32No data—
Sun 1 NovTegelen 11:37+1 min+1 min
Sat 31 OctTegelen 11:36+1 min—
Fri 30 OctNijmegen Heyendaal 12:32No data—
Thu 29 OctNijmegen Heyendaal 12:32No data—
Wed 28 OctNijmegen Heyendaal 12:320 min—
Tue 27 OctNijmegen Heyendaal 12:330 min—
Mon 26 OctNijmegen Heyendaal 12:32No data—
Sun 25 OctTegelen 11:37No data—
Sat 24 OctTegelen 11:36+1 min+1 min
Fri 23 OctTegelen 11:36No data—
Thu 22 OctTegelen 11:37No data—