Train Arriva 32286 Roermond – Venlo

Roermond 23:34 → Venlo 23:57 Daily 0 h 23 min · 5 stops Arriva

It has not run yet today

Last recorded run: Sunday 11 October 0 min

Next service: today 23:34 from Roermond · Mon 12 Oct

Next departure 23:34 today · Roermond
On-time · 30 days
—
Too little data (1/5 runs with data)
RT coverage: 0 full · 1 partial · 4 no data
On-time · 90 days
—
Too little data (1/13 runs with data)
RT coverage: 0 full · 1 partial · 12 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 (5 stops).

StopSched.
23:34
23:39
23:44 / 23:45
23:51
23:57

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 OctTegelen 00:06Partial coverage0 min—
Mon 5 OctNijmegen Heyendaal 01:00No data—
Sun 4 OctBoxmeer 00:44No data—
Sun 27 SeptTegelen 00:05No data—
Sat 26 SeptSwalmen 23:53No data—
Sun 6 SeptTegelen 00:07No data—
Sun 23 AugVierlingsbeek 00:35No data—
Sat 22 AugTegelen 00:05No data—
Sun 16 AugVierlingsbeek 00:36No data—
Sun 9 AugVierlingsbeek 00:37No data—
Sun 2 AugVierlingsbeek 00:36No data—
Sun 26 JulTegelen 00:06No data—
Sun 19 JulTegelen 00:05No data—