Train Arriva 32549 Sittard – Heerlen

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

✓ Today’s run finished

Today, last fix heading to Hoensbroek at 14:18 No data

  1. Sittard13:48
  2. Geleen Oost13:52
  3. Spaubeek13:55
  4. Schinnen13:57
  5. Nuth14:00
  6. Hoensbroek14:04
  7. Heerlen14:08

Next service: tomorrow 13:48 from Sittard · Sat 7 Nov

Next departure 13:48 tomorrow · Sittard
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 0 full · 12 partial · 17 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 0 full · 14 partial · 74 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: +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

  • Thu 8 Oct Max en route +4 min · last fix heading to Hoensbroek +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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