Train Arriva 32289 Nijmegen – Venlo

Nijmegen 00:08 → Venlo 01:00 Mon, Tue, Wed, Thu, Fri 0 h 52 min · 9 stops Arriva

It has not run yet today

Last recorded run: Sunday 11 October 0 min

Next service: tomorrow 00:08 from Nijmegen · Wed 28 Oct

Next departure 00:08 tomorrow · Nijmegen
On-time · 30 days
—
Too little data (1/3 runs with data)
RT coverage: 0 full · 1 partial · 2 no data
On-time · 90 days
—
Too little data (1/12 runs with data)
RT coverage: 0 full · 1 partial · 11 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 so far)

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

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

  • Early 0% · 0
  • On time 100% · 1
  • 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
  • — S n=0
  • 100% S n=1

Stops and timetable

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

StopSched.
00:08
00:11
00:16
00:20 / 00:22
00:29 / 00:32
00:37 / 00:38
00:44 / 00:45
00:58
01:00

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.

Recent runs

DateLast stopFinalMax
Sun 11 OctBlerick 01:12Partial coverage0 min—
Sun 4 OctVierlingsbeek 00:52No data—
Sat 3 OctBoxmeer 00:45No data—
Sun 27 SeptBlerick 01:12No data—
Sun 20 SeptBlerick 01:12No data—
Sun 13 SeptBlerick 01:12No data—
Sun 6 SeptBlerick 01:12No data—
Sun 30 AugBlerick 01:12No data—
Mon 24 AugBlerick 01:12No data—
Mon 17 AugBlerick 01:12No data—
Mon 10 AugBlerick 01:12No data—
Mon 3 AugBlerick 01:12No data—