Train Arriva 32277 Nijmegen – Venlo

Nijmegen 21:08 → Venlo 22:01 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 21:08 from Nijmegen · Fri 13 Nov

Next departure 21:08 today · Nijmegen
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 2 full · 2 partial · 4 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 2 full · 3 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
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

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

  • Early 0% · 0
  • On time 100% · 5
  • 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=3

Stops and timetable

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

Last 90 days, 5 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
21:08on time on time
21:11— —
21:16— —
21:20 / 21:22— —
21:29 / 21:32— —
21:37 / 21:38— —
21:44 / 21:45— —
21:58— —
22:01— —

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 8 NovBlerick 22:12Partial coverage0 min—
Sat 7 NovBlerick 22:12Partial coverage0 min—
Sun 1 NovSwalmen 22:34+1 min—
Sat 31 OctSwalmen 22:34No data—
Sun 25 OctSwalmen 22:35No data—
Sat 24 OctSwalmen 22:34No data—
Sun 18 OctSwalmen 22:36+2 min+2 min
Sat 17 OctSwalmen 22:35No data—
Sun 11 OctBlerick 22:12No data—
Sat 10 OctBlerick 22:12Partial coverage0 min—
Sun 4 OctVierlingsbeek 21:51No data—
Sat 3 OctVierlingsbeek 21:51No data—
Sun 27 SeptBlerick 22:12No data—
Sat 26 SeptBlerick 22:12No data—
Sun 20 SeptBlerick 22:12No data—
Sat 19 SeptBlerick 22:12No data—
Sun 13 SeptBlerick 22:12No data—
Sat 12 SeptBlerick 22:12No data—
Sun 6 SeptBlerick 22:13No data—
Sat 5 SeptBlerick 22:12No data—
Sun 30 AugBlerick 22:14No data—
Sat 29 AugBlerick 22:12No data—
Sun 23 AugBlerick 22:12No data—
Sat 22 AugSwalmen 22:36No data—
Sun 16 AugBlerick 22:12No data—