Train Arriva 32579 Sittard – Heerlen

Sittard 21:18 → Heerlen 21:38 Daily 0 h 20 min · 7 stops Arriva

It has not run yet today

Last recorded run: Saturday 14 November +2 min

Next service: today 21:18 from Sittard · Sun 15 Nov

Next departure 21:18 today · Sittard
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 4 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 0 full · 7 partial · 18 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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 10 Oct Max en route +4 min · last fix heading to Hoensbroek +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 6
  • 3–10 min 14% · 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=4

Stops and timetable

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

Last 90 days, 7 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:18on time on time
21:22— —
21:25— —
21:27— —
21:30— —
21:34— —
21:38— —

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