Train Arriva 32573 Sittard – Heerlen

Sittard 19:48 → Heerlen 20:08 Daily 0 h 20 min · 7 stops Arriva

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 19:48 from Sittard · Mon 16 Nov

Next departure 19:48 today · Sittard
On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 0 full · 6 partial · 3 no data
On-time · 90 days
88%
7/8 runs under 3 min
RT coverage: 0 full · 8 partial · 20 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Heerlen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 7 Nov Max en route +4 min · last fix heading to Hoensbroek +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 7
  • 3–10 min 13% · 1
  • 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
  • 67% S n=3
  • 100% S n=5

Stops and timetable

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

Last 90 days, 8 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
19:48on time on time
19:52— —
19:55— —
19:57— —
20:00— —
20:04— —
20:08— —

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 NovHoensbroek 20:18Partial coverage0 min—
Sat 14 NovHoensbroek 20:19Partial coverage+1 min+1 min
Sun 8 NovHoensbroek 20:18Partial coverage0 min—
Sat 7 NovHoensbroek 20:19Partial coverage+4 min+4 min
Sun 1 NovHoensbroek 20:19Partial coverage0 min—
Sat 31 OctHoensbroek 20:18No data—
Sun 25 OctHoensbroek 20:19No data—
Sat 24 OctHoensbroek 20:18No data—
Sun 18 OctHoensbroek 20:18Partial coverage0 min—
Sat 17 OctHoensbroek 20:20No data—
Fri 16 OctSpaubeek 20:09No data—
Sun 11 OctHoensbroek 20:19Partial coverage+2 min+2 min
Sat 10 OctHoensbroek 20:19Partial coverage+1 min—
Sun 4 OctHoensbroek 20:22No data—
Sat 3 OctHoensbroek 20:19No data—
Sun 27 SeptHoensbroek 20:18No data—
Sat 26 SeptHoensbroek 20:21No data—
Sun 20 SeptHoensbroek 20:18No data—
Sat 19 SeptHoensbroek 20:18No data—
Sun 13 SeptHoensbroek 20:19No data—
Sat 12 SeptHoensbroek 20:19No data—
Sun 6 SeptHoensbroek 20:18No data—
Sat 5 SeptHoensbroek 20:18No data—
Sun 30 AugHoensbroek 20:19No data—
Sat 29 AugHoensbroek 20:19No data—
Sun 23 AugHoensbroek 20:18No data—
Sat 22 AugHoensbroek 20:18No data—
Fri 21 AugHoensbroek 20:18No data—