Train Arriva 32567 Sittard – Heerlen

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

✓ Today’s run finished

Today, last fix heading to Hoensbroek at 19:03 +16 min

  1. Sittard18:18
  2. Geleen Oost18:22
  3. Spaubeek18:25
  4. Schinnen18:27
  5. Nuth18:30
  6. Hoensbroek18:34
  7. Heerlen18:38

Next service: tomorrow 18:18 from Sittard · Mon 16 Nov

Next departure 18:18 tomorrow · Sittard
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 0 full · 12 partial · 7 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 0 full · 16 partial · 39 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: +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

  • Sun 15 Nov Max en route +16 min · last fix heading to Hoensbroek +16 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • — W n=0
  • 100% T n=1
  • 100% F n=3
  • 100% S n=4
  • 80% S n=5

Stops and timetable

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

Last 90 days, 16 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
18:18on time +1 min
18:22— —
18:25— —
18:27— —
18:30— —
18:34— —
18: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
Sun 15 NovHoensbroek 19:03Partial coverage+16 min+16 min
Sat 14 NovHoensbroek 18:48Partial coverage0 min—
Fri 13 NovHoensbroek 18:48Partial coverage+2 min+3 min
Thu 12 NovGeleen Oost 18:34Partial coverage0 min—
Tue 10 NovSittard 18:32Partial coverage+1 min+1 min
Sun 8 NovHoensbroek 18:48Partial coverage0 min—
Sat 7 NovHoensbroek 18:48Partial coverage0 min—
Fri 6 NovHoensbroek 18:44Partial coverage+1 min—
Sun 1 NovHoensbroek 18:48Partial coverage0 min—
Sat 31 OctHoensbroek 18:49Partial coverage+2 min+2 min
Fri 30 OctHoensbroek 18:48No data—
Sun 25 OctHoensbroek 18:49No data—
Sat 24 OctHoensbroek 18:54No data—
Thu 22 OctHoensbroek 18:48No data—
Wed 21 OctHoensbroek 18:48No data—
Tue 20 OctHoensbroek 18:48Partial coverage0 min—
Mon 19 OctHoensbroek 18:48No data—
Sun 18 OctHoensbroek 18:50Partial coverage+1 min+2 min
Sat 17 OctHoensbroek 18:48No data—
Fri 16 OctHoensbroek 18:48No data—
Thu 15 OctNuth 18:44No data—
Tue 13 OctHoensbroek 18:48No data—
Mon 12 OctHoensbroek 18:48Partial coverage0 min—
Sun 11 OctHoensbroek 18:49Partial coverage+1 min+1 min
Sat 10 OctHoensbroek 18:51Partial coverage+1 min+2 min
Fri 9 OctHoensbroek 18:48Partial coverage+1 min+1 min
Sun 4 OctHoensbroek 18:49No data—
Sat 3 OctHoensbroek 18:48No data—
Fri 2 OctHoensbroek 18:48No data—
Sun 27 SeptHoensbroek 18:50No data—