Train Arriva 32229 Nijmegen – Venlo

Nijmegen 09:08 → Venlo 10:01 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Thursday 19 November +2 min

Next service: today 09:08 from Nijmegen · Fri 20 Nov

Next departure 09:08 today · Nijmegen
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 16 full · 2 partial · 11 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 24 full · 2 partial · 61 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

Worst days

  • Sat 10 Oct Max en route +10 min · last fix heading to Swalmen +9 min
  • Mon 16 Nov Max en route +5 min · last fix heading to Swalmen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 24
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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