Train Arriva 32558 Heerlen – Sittard

Heerlen 16:52 → Sittard 17:12 Daily 0 h 20 min · 7 stops Arriva

It has not run yet today

Last recorded run: Sunday 15 November +2 min

Next service: today 16:52 from Heerlen · Mon 16 Nov

Next departure 16:52 today · Heerlen
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 0 full · 18 partial · 11 no data
On-time · 90 days
88%
22/25 runs under 3 min
RT coverage: 0 full · 25 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Sat 31 Oct Max en route +5 min · last fix heading to Geleen Oost +5 min
  • Fri 13 Nov Max en route +4 min · last fix heading to Geleen Oost +4 min
  • Sun 8 Nov Max en route +4 min · last fix heading to Geleen Oost +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 22
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=4
  • 100% T n=2
  • 67% F n=3
  • 80% S n=5
  • 80% S n=5

Stops and timetable

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

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