Train Arriva 32227 Nijmegen – Venlo

Nijmegen 08:38 → Venlo 09:31 Daily 0 h 53 min · 9 stops Arriva

✓ Today’s run finished

Today, last fix heading to Blerick at 09:44 +2 min

  1. Nijmegen08:38
  2. Nijmegen Heyendaal08:41
  3. Cuijk08:50
  4. Boxmeer08:59
  5. Vierlingsbeek09:07
  6. Blerick09:28
  7. Venlo09:31

Next service: tomorrow 08:38 from Nijmegen · Thu 19 Nov

Next departure 08:38 tomorrow · Nijmegen
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 14 full · 1 partial · 15 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 22 full · 1 partial · 65 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Sun 11 Oct Max en route +6 min · last fix heading to Swalmen +6 min
  • Sun 18 Oct Max en route +6 min · last fix heading to Swalmen +5 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Swalmen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 20
  • 3–10 min 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
08:38on time on time
08:41≈ on time ≈ on time
08:46≈ on time ≈ +1 min
08:50 / 08:52≈ on time ≈ +1 min
08:59 / 09:02≈ on time ≈ +2 min
09:07 / 09:08≈ on time ≈ +2 min
09:14 / 09:15≈ on time ≈ +3 min
09:28≈ on time ≈ +4 min
09:31on time +4 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 NovBlerick 09:44Partial coverage+2 min+2 min
Tue 17 NovSwalmen 10:07+2 min+3 min
Mon 16 NovSwalmen 10:040 min—
Sun 15 NovSwalmen 10:04No data—
Sat 14 NovSwalmen 10:040 min+1 min
Fri 13 NovSwalmen 10:04+1 min+1 min
Thu 12 NovSwalmen 10:09+4 min+5 min
Wed 11 NovSwalmen 10:04+1 min—
Tue 10 NovSwalmen 10:040 min+1 min
Mon 9 NovSwalmen 10:04+1 min+1 min
Sun 8 NovSwalmen 10:040 min—
Sat 7 NovSwalmen 10:040 min+1 min
Fri 6 NovSwalmen 10:04No data—
Thu 5 NovSwalmen 10:04No data—
Wed 4 NovSwalmen 10:040 min—
Tue 3 NovSwalmen 10:07No data—
Mon 2 NovSwalmen 10:04No data—
Sun 1 NovSwalmen 10:04No data—
Sat 31 OctSwalmen 10:04No data—
Fri 30 OctSwalmen 10:04No data—
Thu 29 OctSwalmen 10:05No data—
Wed 28 OctSwalmen 10:100 min—
Tue 27 OctSwalmen 10:060 min—
Mon 26 OctSwalmen 10:04No data—
Sun 25 OctSwalmen 10:05No data—
Sat 24 OctSwalmen 10:04No data—
Fri 23 OctSwalmen 10:04No data—
Thu 22 OctSwalmen 10:08No data—
Wed 21 OctSwalmen 10:04No data—
Tue 20 OctSwalmen 10:040 min—