Train Arriva 32283 Nijmegen – Venlo

Nijmegen 22:38 → Venlo 23:31 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: tomorrow 22:38 from Nijmegen · Wed 18 Nov

Next departure 22:38 tomorrow · Nijmegen
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 2 full · 2 partial · 2 no data
On-time · 90 days
100%
6/6 runs under 3 min
RT coverage: 3 full · 3 partial · 17 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=2
  • 100% S n=4

Stops and timetable

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

Last 90 days, 6 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
22:38on time on time
22:41— —
22:46— —
22:50 / 22:52— —
22:59 / 23:02— —
23:07 / 23:08— —
23:14 / 23:15— —
23:28— —
23:31— —

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 15 NovBlerick 23:42Partial coverage0 min—
Sat 14 NovBoxmeer 23:140 min—
Sun 8 NovBlerick 23:42Partial coverage0 min—
Sat 7 NovVenray 23:240 min—
Sun 1 NovSwalmen 00:04No data—
Sun 25 OctSwalmen 00:04No data—
Sun 18 OctSwalmen 00:050 min+1 min
Sat 17 OctSwalmen 00:06No data—
Sun 11 OctBlerick 23:42Partial coverage0 min—
Sun 4 OctVierlingsbeek 23:22No data—
Sat 3 OctVierlingsbeek 23:22No data—
Sun 27 SeptBlerick 23:42No data—
Sat 26 SeptTegelen 23:52No data—
Sun 20 SeptBlerick 23:42No data—
Sat 19 SeptBoxmeer 23:08No data—
Sun 13 SeptBlerick 23:45No data—
Sat 12 SeptBlerick 23:42No data—
Sun 6 SeptBlerick 23:42No data—
Sat 5 SeptCuijk 23:06No data—
Sun 30 AugBlerick 23:42No data—
Sat 29 AugNijmegen Heyendaal 22:55No data—
Sun 23 AugSwalmen 00:06No data—
Sat 22 AugSwalmen 00:04No data—