Train Arriva 32565 Sittard – Heerlen

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

✓ Today’s run finished

Today, last fix heading to Hoensbroek at 18:24 +7 min

  1. Sittard17:48
  2. Geleen Oost17:52
  3. Spaubeek17:55
  4. Schinnen17:57
  5. Nuth18:00
  6. Hoensbroek18:04
  7. Heerlen18:08

Next service: tomorrow 17:48 from Sittard · Mon 16 Nov

Next departure 17:48 tomorrow · Sittard
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 0 full · 15 partial · 14 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 1 full · 22 partial · 64 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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 +7 min · last fix heading to Hoensbroek +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
17:48on time on time
17:52— —
17:55— —
17:57— —
18:00— —
18:04— —
18: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 18:24Partial coverage+7 min+7 min
Sat 14 NovHoensbroek 18:18Partial coverageNo data—
Fri 13 NovHoensbroek 18:18Partial coverage+2 min+2 min
Thu 12 NovHoensbroek 18:18Partial coverage+1 min—
Wed 11 NovHoensbroek 18:18Partial coverage+2 min+2 min
Tue 10 NovHoensbroek 18:18Partial coverage+1 min—
Mon 9 NovHoensbroek 18:18Partial coverage0 min—
Sun 8 NovHoensbroek 18:18Partial coverage0 min—
Sat 7 NovHoensbroek 18:18Partial coverage+1 min—
Fri 6 NovHoensbroek 18:18Partial coverage+1 min+1 min
Thu 5 NovHoensbroek 18:18No data—
Wed 4 NovHoensbroek 18:18No data—
Mon 2 NovHoensbroek 18:18No data—
Sun 1 NovHoensbroek 18:18Partial coverage0 min—
Sat 31 OctHoensbroek 18:18Partial coverage0 min—
Fri 30 OctHoensbroek 18:18No data—
Thu 29 OctNuth 18:14No data—
Wed 28 OctHoensbroek 18:18Partial coverage0 min—
Tue 27 OctHoensbroek 18:18No data—
Mon 26 OctHoensbroek 18:18Partial coverage+1 min+1 min
Sun 25 OctHoensbroek 18:31No data—
Sat 24 OctHoensbroek 18:22No data—
Fri 23 OctHoensbroek 18:19No data—
Thu 22 OctHoensbroek 18:18No data—
Wed 21 OctHoensbroek 18:18No data—
Tue 20 OctHoensbroek 18:18Partial coverage0 min—
Mon 19 OctHoensbroek 18:18No data—
Sun 18 OctHoensbroek 18:19Partial coverage+2 min+3 min
Sat 17 OctHoensbroek 18:18No data—
Fri 16 OctHoensbroek 18:18No data—