Train Arriva 32239 Nijmegen – Venlo

Nijmegen 11:38 → Venlo 12:31 Daily 0 h 53 min · 9 stops Arriva

✓ Today’s run finished

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

  1. Nijmegen11:38
  2. Nijmegen Heyendaal11:41
  3. Cuijk11:50
  4. Boxmeer11:59
  5. Vierlingsbeek12:07
  6. Blerick12:28
  7. Venlo12:31

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

Next departure 11:38 tomorrow · Nijmegen
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 18 full · 1 partial · 11 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 26 full · 1 partial · 61 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

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

  • Early 0% · 0
  • On time 100% · 27
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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