Train Arriva 32491 Roermond – Sittard

Roermond 00:34 → Sittard 00:52 Daily 0 h 18 min · 4 stops Arriva

It has not run yet today

Last recorded run: Monday 26 October No data

Next service: tomorrow 00:34 from Roermond · Sat 31 Oct

Next departure 00:34 tomorrow · Roermond
On-time · 30 days
—
Too little data (2/6 runs with data)
RT coverage: 1 full · 1 partial · 4 no data
On-time · 90 days
—
Too little data (2/14 runs with data)
RT coverage: 1 full · 1 partial · 12 no data
Typical delay
—
Needs at least 5 runs with data (2 so far)
P90
—
Needs at least 5 runs with data (2 so far)

Last 30 days

Arrival delay at Sittard, 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

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

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

On-time by weekday

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

Stops and timetable

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

StopSched.
00:34
00:42
00:46
00:52

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
Mon 26 OctSusteren 01:08No data—
Mon 19 OctSusteren 01:02Partial coverage0 min—
Sun 18 OctSusteren 01:00No data—
Mon 12 OctSusteren 01:010 min—
Mon 5 OctSusteren 01:04No data—
Sun 4 OctRoermond 00:48No data—
Mon 28 SeptSusteren 01:01No data—
Mon 21 SeptSusteren 01:01No data—
Mon 14 SeptSusteren 01:01No data—
Mon 31 AugSusteren 01:07No data—
Mon 24 AugSusteren 01:04No data—
Mon 17 AugSusteren 01:01No data—
Mon 10 AugSusteren 01:04No data—
Mon 3 AugSusteren 01:01No data—