Train Arriva 32514 Heerlen – Sittard

Heerlen 05:52 → Sittard 06:12 Mon, Tue, Wed, Thu, Fri 0 h 20 min · 7 stops Arriva

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 05:52 from Heerlen · Mon 9 Nov

Next departure 05:52 tomorrow · Heerlen
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 0 full · 17 partial · 1 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 0 full · 21 partial · 40 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 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 +3 min · last fix heading to Geleen Oost +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
05:52on time on time
05:56— —
05:59— —
06:02— —
06:04— —
06:08— —
06:12— —

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 NovGeleen Oost 06:24No data—
Thu 5 NovGeleen Oost 06:24Partial coverage+2 min+2 min
Wed 4 NovGeleen Oost 06:23Partial coverage+1 min—
Tue 3 NovGeleen Oost 06:23Partial coverage+3 min+3 min
Fri 30 OctGeleen Oost 06:23Partial coverage+1 min+1 min
Thu 29 OctGeleen Oost 06:22Partial coverage0 min—
Wed 28 OctGeleen Oost 06:25Partial coverage+3 min+3 min
Tue 27 OctGeleen Oost 06:24Partial coverage0 min—
Mon 26 OctGeleen Oost 06:23Partial coverage+1 min+1 min
Fri 23 OctGeleen Oost 06:23Partial coverage+1 min—
Thu 22 OctGeleen Oost 06:23Partial coverage+1 min+1 min
Wed 21 OctGeleen Oost 06:22Partial coverage+1 min—
Tue 20 OctGeleen Oost 06:23Partial coverage+1 min—
Mon 19 OctGeleen Oost 06:22Partial coverage+1 min—
Fri 16 OctGeleen Oost 06:23Partial coverage+2 min+2 min
Thu 15 OctGeleen Oost 06:23Partial coverage+2 min+2 min
Tue 13 OctGeleen Oost 06:22Partial coverage0 min—
Mon 12 OctGeleen Oost 06:23Partial coverage0 min—
Fri 9 OctGeleen Oost 06:23Partial coverage0 min—
Thu 8 OctGeleen Oost 06:22Partial coverage0 min—
Wed 7 OctGeleen Oost 06:22Partial coverage0 min—
Tue 6 OctGeleen Oost 06:23Partial coverage+1 min—
Mon 5 OctGeleen Oost 06:23No data—
Fri 2 OctGeleen Oost 06:22No data—
Thu 1 OctGeleen Oost 06:23No data—
Wed 30 SeptGeleen Oost 06:22No data—
Tue 29 SeptGeleen Oost 06:22No data—
Mon 28 SeptGeleen Oost 06:22No data—
Fri 25 SeptGeleen Oost 06:22No data—
Thu 24 SeptGeleen Oost 06:22No data—