Train Arriva 32516 Heerlen – Sittard

Heerlen 06:22 → Sittard 06:42 Mon, Tue, Wed, Thu, Fri, Sat 0 h 20 min · 7 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November No data

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

Next departure 06:22 today · Heerlen
On-time · 30 days
81%
17/21 runs under 3 min
RT coverage: 0 full · 21 partial · 2 no data
On-time · 90 days
82%
18/22 runs under 3 min
RT coverage: 0 full · 22 partial · 51 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Wed 28 Oct Max en route +16 min · last fix heading to Geleen Oost +16 min
  • Tue 13 Oct Max en route +4 min · last fix heading to Geleen Oost +4 min
  • Fri 30 Oct Max en route +4 min · last fix heading to Geleen Oost +4 min
  • Tue 3 Nov Max en route +3 min · last fix heading to Geleen Oost +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 18
  • 3–10 min 14% · 3
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 60% T n=5
  • 67% W n=3
  • 100% T n=3
  • 75% F n=4
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
06:22on time on time
06:26— —
06:29— —
06:32— —
06:34— —
06:38— —
06: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 06:52Partial coverageNo data—
Tue 3 NovGeleen Oost 06:54Partial coverage+3 min+3 min
Sat 31 OctGeleen Oost 06:53Partial coverage+1 min—
Fri 30 OctGeleen Oost 06:55Partial coverage+4 min+4 min
Thu 29 OctGeleen Oost 06:53Partial coverage+1 min—
Wed 28 OctGeleen Oost 07:08Partial coverage+16 min+16 min
Tue 27 OctGeleen Oost 06:53Partial coverage+1 min+1 min
Mon 26 OctGeleen Oost 06:54Partial coverage+1 min+1 min
Sat 24 OctGeleen Oost 06:54Partial coverage+1 min+1 min
Fri 23 OctGeleen Oost 06:53Partial coverage+1 min—
Thu 22 OctGeleen Oost 06:52Partial coverageNo data—
Wed 21 OctGeleen Oost 06:54Partial coverage+1 min+1 min
Tue 20 OctGeleen Oost 06:53Partial coverage+1 min+1 min
Mon 19 OctGeleen Oost 06:53Partial coverage+1 min+1 min
Sat 17 OctGeleen Oost 06:53Partial coverage0 min—
Fri 16 OctGeleen Oost 06:53Partial coverage+1 min—
Thu 15 OctGeleen Oost 06:53Partial coverage0 min—
Tue 13 OctGeleen Oost 06:57Partial coverage+4 min+4 min
Mon 12 OctGeleen Oost 06:53Partial coverage0 min—
Sat 10 OctGeleen Oost 06:53Partial coverage+1 min—
Fri 9 OctGeleen Oost 06:52Partial coverage0 min—
Thu 8 OctGeleen Oost 06:55Partial coverage+2 min+3 min
Wed 7 OctGeleen Oost 06:53Partial coverage0 min+1 min
Tue 6 OctGeleen Oost 06:53Partial coverage0 min—
Mon 5 OctGeleen Oost 06:53No data—
Sat 3 OctGeleen Oost 06:52No data—
Fri 2 OctGeleen Oost 06:53No data—
Thu 1 OctGeleen Oost 06:53No data—
Wed 30 SeptGeleen Oost 06:53No data—
Tue 29 SeptGeleen Oost 06:53No data—