Train Arriva 32519 Sittard – Heerlen

Sittard 06:18 → Heerlen 06:38 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 06:18 from Sittard · Mon 9 Nov

Next departure 06:18 tomorrow · Sittard
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 0 full · 15 partial · 3 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 0 full · 18 partial · 43 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Wed 28 Oct Max en route +8 min · last fix heading to Hoensbroek +8 min
  • Fri 30 Oct Max en route +5 min · last fix heading to Hoensbroek +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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:18on time on time
06:22— —
06:25— —
06:27— —
06:30— —
06:34— —
06:38— —

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