Train Arriva 32249 Nijmegen – Venlo

Nijmegen 14:08 → Venlo 15:01 Daily 0 h 53 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Blerick at 15:12 0 min

  1. Nijmegen14:08
  2. Nijmegen Heyendaal14:11
  3. Cuijk14:20
  4. Boxmeer14:29
  5. Vierlingsbeek14:37
  6. Blerick14:58
  7. Venlo15:01

Next service: tomorrow 14:08 from Nijmegen · Mon 9 Nov

Next departure 14:08 tomorrow · Nijmegen
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 9 full · 2 partial · 18 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 14 full · 2 partial · 72 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: +2 min

Last 30 days

Arrival delay at Venlo, 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

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

  • Early 0% · 0
  • On time 100% · 16
  • 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=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 16 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
14:08on time on time
14:11≈ on time ≈ on time
14:16≈ on time ≈ on time
14:20 / 14:22≈ on time ≈ +1 min
14:29 / 14:32≈ on time ≈ +1 min
14:37 / 14:38≈ on time ≈ +1 min
14:44 / 14:45≈ on time ≈ +2 min
14:58≈ on time ≈ +2 min
15:01on 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
Sun 8 NovBlerick 15:12Partial coverage0 min—
Sat 7 NovSwalmen 15:34+1 min+2 min
Fri 6 NovSwalmen 15:34No data—
Thu 5 NovSwalmen 15:35No data—
Wed 4 NovSwalmen 15:38+3 min+3 min
Tue 3 NovSwalmen 15:38No data—
Mon 2 NovSwalmen 15:34No data—
Sun 1 NovSwalmen 15:35No data—
Sat 31 OctSwalmen 15:34No data—
Fri 30 OctSwalmen 15:35No data—
Thu 29 OctSwalmen 15:35No data—
Wed 28 OctSwalmen 15:340 min—
Tue 27 OctSwalmen 15:370 min—
Mon 26 OctSwalmen 15:38No data—
Sun 25 OctSwalmen 15:34No data—
Sat 24 OctSwalmen 15:35+1 min+1 min
Fri 23 OctSwalmen 15:36No data—
Thu 22 OctSwalmen 15:34No data—
Wed 21 OctSwalmen 15:35No data—
Tue 20 OctSwalmen 15:350 min—
Mon 19 OctSwalmen 15:35No data—
Sun 18 OctSwalmen 15:350 min+1 min
Sat 17 OctSwalmen 15:35No data—
Fri 16 OctSwalmen 15:37No data—
Thu 15 OctSwalmen 15:34No data—
Tue 13 OctSwalmen 15:35No data—
Mon 12 OctSwalmen 15:36+1 min+1 min
Sun 11 OctBlerick 15:14Partial coverage+2 min+2 min
Sat 10 OctSwalmen 15:340 min—
Fri 9 OctSwalmen 15:340 min—