Train Arriva 32544 Heerlen – Sittard

Heerlen 13:22 → Sittard 13:42 Daily 0 h 20 min · 7 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 13:22 from Heerlen · Thu 5 Nov

Next departure 13:22 today · Heerlen
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 0 full · 14 partial · 14 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 0 full · 16 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Sittard, 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 +6 min · last fix heading to Geleen Oost +6 min
  • Sun 18 Oct Max en route +6 min · last fix heading to Geleen Oost +6 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 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
13:22on time on time
13:26— —
13:29— —
13:32— —
13:34— —
13:38— —
13:42— —

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
Wed 4 NovGeleen Oost 13:53Partial coverage0 min+1 min
Tue 3 NovGeleen Oost 13:53No data—
Mon 2 NovGeleen Oost 13:52No data—
Sun 1 NovGeleen Oost 13:54Partial coverage0 min—
Sat 31 OctGeleen Oost 13:53Partial coverage+1 min—
Fri 30 OctGeleen Oost 13:53No data—
Thu 29 OctGeleen Oost 13:52Partial coverage0 min—
Wed 28 OctGeleen Oost 13:53Partial coverage0 min—
Tue 27 OctGeleen Oost 13:52Partial coverage0 min—
Mon 26 OctGeleen Oost 13:54No data—
Sun 25 OctGeleen Oost 13:58No data—
Sat 24 OctGeleen Oost 13:55Partial coverage+3 min+3 min
Fri 23 OctGeleen Oost 13:52No data—
Thu 22 OctGeleen Oost 13:53No data—
Wed 21 OctGeleen Oost 13:53No data—
Tue 20 OctGeleen Oost 13:52Partial coverage0 min—
Mon 19 OctGeleen Oost 13:54No data—
Sun 18 OctGeleen Oost 13:59Partial coverage+6 min+6 min
Sat 17 OctGeleen Oost 13:52No data—
Fri 16 OctGeleen Oost 13:52No data—
Thu 15 OctGeleen Oost 13:52No data—
Tue 13 OctGeleen Oost 13:53No data—
Mon 12 OctGeleen Oost 13:52No data—
Sun 11 OctGeleen Oost 13:52Partial coverage0 min—
Sat 10 OctGeleen Oost 13:53Partial coverage+1 min+1 min
Fri 9 OctGeleen Oost 13:52Partial coverage0 min—
Thu 8 OctGeleen Oost 13:54Partial coverage+6 min+6 min
Wed 7 OctGeleen Oost 13:52Partial coverage0 min—
Tue 6 OctGeleen Oost 13:52Partial coverage0 min—
Mon 5 OctGeleen Oost 13:52Partial coverage0 min—