Train Arriva 32249 Nijmegen → Venlo

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

Arriva 32249 Nijmegen–Venlo: final delay under 3 min on 16 of its 20 runs with data in the last 30 days (80%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 17:51 (GMT+1).

✓ 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 23 Nov

Next departure 14:08 tomorrow · Nijmegen
On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 15 full · 5 partial · 10 no data
On-time · 90 days
87%
26/30 runs under 3 min
RT coverage: 25 full · 5 partial · 58 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

Worst days

  • Mon 16 Nov Max en route +7 min · last fix heading to Swalmen +6 min
  • Thu 19 Nov Max en route +5 min · last fix heading to Blerick +4 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Swalmen +4 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Swalmen +3 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 87% · 26
  • 3–10 min 13% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=5
  • 80% W n=5
  • 67% T n=3
  • 67% F n=3
  • 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
14:08on time on time
14:11≈ on time ≈ on time
14:16≈ on time ≈ +1 min
14:20 / 14:22≈ on time ≈ +1 min
14:29 / 14:32≈ on time ≈ +1 min
14:37 / 14:38≈ on time ≈ +2 min
14:44 / 14:45≈ on time ≈ +2 min
14:58≈ +1 min ≈ +3 min
15:01+1 min +3 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 22 NovBlerick 15:12Partial coverage0 min—
Sat 21 NovBlerick 15:12Partial coverage0 min—
Fri 20 NovBlerick 15:13Partial coverage+1 min+1 min
Thu 19 NovBlerick 15:17Partial coverage+4 min+5 min
Wed 18 NovBlerick 15:13Partial coverage+1 min+1 min
Tue 17 NovSwalmen 15:340 min—
Mon 16 NovSwalmen 15:39+6 min+7 min
Sun 15 NovSwalmen 15:390 min+3 min
Sat 14 NovSwalmen 15:34+1 min—
Fri 13 NovSwalmen 15:39+4 min+5 min
Thu 12 NovSwalmen 15:34+2 min+2 min
Wed 11 NovSwalmen 15:39+3 min+4 min
Tue 10 NovSwalmen 15:38+3 min+3 min
Mon 9 NovSwalmen 15:340 min—
Sun 8 NovBlerick 15:120 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