Train Arriva 32560 Heerlen – Sittard

Heerlen 17:22 → Sittard 17:42 Daily 0 h 20 min · 7 stops Arriva

✓ Today’s run finished

Today, last fix heading to Geleen Oost at 17:52 No data

  1. Heerlen17:22
  2. Hoensbroek17:26
  3. Nuth17:29
  4. Schinnen17:32
  5. Spaubeek17:34
  6. Geleen Oost17:38
  7. Sittard17:42

Next service: tomorrow 17:22 from Heerlen · Fri 6 Nov

Next departure 17:22 tomorrow · Heerlen
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 0 full · 11 partial · 17 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 0 full · 13 partial · 74 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

  • Mon 26 Oct Max en route +8 min · last fix heading to Geleen Oost +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=1
  • 100% F n=1
  • 100% S n=2
  • 100% S n=2

Stops and timetable

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

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