Train Arriva 32244 Venlo – Nijmegen

Venlo 13:29 → Nijmegen 14:22 Daily 0 h 53 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Nijmegen Heyendaal at 14:34 +1 min

  1. Venlo13:29
  2. Blerick13:31
  3. Vierlingsbeek13:50
  4. Boxmeer13:56
  5. Cuijk14:07
  6. Nijmegen Heyendaal14:18
  7. Nijmegen14:22

Next service: tomorrow 13:29 from Venlo · Thu 19 Nov

Next departure 13:29 tomorrow · Venlo
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 21 full · 1 partial · 8 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 29 full · 1 partial · 58 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: +3 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 11 Nov Max en route +15 min · last fix heading to Nijmegen Heyendaal +14 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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