Train Arriva 32263 Nijmegen – Venlo

Nijmegen 17:38 → Venlo 18:31 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Wednesday 18 November +1 min

Next service: today 17:38 from Nijmegen · Thu 19 Nov

Next departure 17:38 today · Nijmegen
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 18 full · 1 partial · 10 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 28 full · 1 partial · 57 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

  • Fri 13 Nov Max en route +7 min · last fix heading to Swalmen +7 min
  • Sun 15 Nov Max en route +7 min · last fix heading to Swalmen +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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