Train Arriva 32542 Heerlen – Sittard

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

✓ Today’s run finished

Today, last fix heading to Geleen Oost at 13:22 No data

  1. Heerlen12:52
  2. Hoensbroek12:56
  3. Nuth12:59
  4. Schinnen13:02
  5. Spaubeek13:04
  6. Geleen Oost13:08
  7. Sittard13:12

Next service: tomorrow 12:52 from Heerlen · Fri 6 Nov

Next departure 12:52 tomorrow · Heerlen
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 17 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 74 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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