Train Arriva 32566 Heerlen – Sittard

Heerlen 18:52 → Sittard 19:12 Daily 0 h 20 min · 7 stops Arriva

It has not run yet today

Last recorded run: Sunday 15 November +3 min

Next service: tomorrow 18:52 from Heerlen · Tue 17 Nov

Next departure 18:52 tomorrow · Heerlen
On-time · 30 days
67%
6/9 runs under 3 min
RT coverage: 0 full · 9 partial · 3 no data
On-time · 90 days
73%
8/11 runs under 3 min
RT coverage: 0 full · 11 partial · 25 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sun 15 Nov Max en route +4 min · last fix heading to Geleen Oost +3 min
  • Fri 23 Oct Max en route +3 min · last fix heading to Geleen Oost +3 min
  • Sun 18 Oct Max en route +3 min · last fix heading to Geleen Oost +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 73% · 8
  • 3–10 min 27% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 50% F n=2
  • 100% S n=4
  • 60% S n=5

Stops and timetable

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

Last 90 days, 11 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
18:52on time on time
18:56— —
18:59— —
19:02— —
19:04— —
19:08— —
19: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
Sun 15 NovGeleen Oost 19:24Partial coverage+3 min+4 min
Sat 14 NovGeleen Oost 19:22Partial coverage0 min—
Fri 13 NovHoensbroek 19:09Partial coverage0 min—
Sun 8 NovGeleen Oost 19:24Partial coverage+2 min+2 min
Sat 7 NovGeleen Oost 19:24Partial coverage+2 min+2 min
Sun 1 NovGeleen Oost 19:23Partial coverage0 min—
Sat 31 OctGeleen Oost 19:23Partial coverage+1 min—
Fri 30 OctHeerlen 19:06No data—
Sun 25 OctGeleen Oost 19:25No data—
Sat 24 OctGeleen Oost 19:40No data—
Fri 23 OctGeleen Oost 19:22Partial coverage+3 min+3 min
Sun 18 OctGeleen Oost 19:25Partial coverage+3 min+3 min
Sat 17 OctGeleen Oost 19:22No data—
Fri 16 OctGeleen Oost 19:22No data—
Sun 11 OctGeleen Oost 19:22Partial coverage0 min—
Sat 10 OctGeleen Oost 19:22Partial coverage+1 min—
Sun 4 OctGeleen Oost 19:23No data—
Sat 3 OctGeleen Oost 19:22No data—
Sun 27 SeptGeleen Oost 19:23No data—
Sat 26 SeptGeleen Oost 19:23No data—
Sun 20 SeptGeleen Oost 19:22No data—
Sat 19 SeptGeleen Oost 19:23No data—
Sun 13 SeptGeleen Oost 19:22No data—
Sat 12 SeptGeleen Oost 19:22No data—
Sun 6 SeptGeleen Oost 19:22No data—
Sat 5 SeptGeleen Oost 19:22No data—
Fri 4 SeptHeerlen 19:06No data—
Sun 30 AugGeleen Oost 19:22No data—
Sat 29 AugGeleen Oost 19:22No data—
Fri 28 AugGeleen Oost 19:22No data—