Train Arriva 32543 Sittard – Heerlen

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

✓ Today’s run finished

Today, last fix heading to Hoensbroek at 12:49 No data

  1. Sittard12:18
  2. Geleen Oost12:22
  3. Spaubeek12:25
  4. Schinnen12:27
  5. Nuth12:30
  6. Hoensbroek12:34
  7. Heerlen12:38

Next service: tomorrow 12:18 from Sittard · Sat 7 Nov

Next departure 12:18 tomorrow · Sittard
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 18 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
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

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=2
  • 100% W n=2
  • 100% T n=2
  • 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:18on time on time
12:22— —
12:25— —
12:27— —
12:30— —
12:34— —
12: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 12:49No data—
Thu 5 NovHoensbroek 12:48No data—
Wed 4 NovHoensbroek 12:48No data—
Tue 3 NovHoensbroek 12:49Partial coverage0 min—
Mon 2 NovHoensbroek 12:48No data—
Sun 1 NovHoensbroek 12:50Partial coverage+1 min+2 min
Sat 31 OctHoensbroek 12:48Partial coverage0 min—
Fri 30 OctHoensbroek 12:48No data—
Thu 29 OctHoensbroek 12:49Partial coverage0 min—
Wed 28 OctHoensbroek 12:48Partial coverage0 min—
Tue 27 OctHoensbroek 12:50No data—
Mon 26 OctHoensbroek 12:48No data—
Sun 25 OctHoensbroek 12:48No data—
Sat 24 OctHoensbroek 12:49Partial coverage+1 min+1 min
Fri 23 OctHoensbroek 12:49No data—
Thu 22 OctHoensbroek 12:54No data—
Wed 21 OctHoensbroek 12:49No data—
Tue 20 OctHoensbroek 12:48No data—
Mon 19 OctHoensbroek 12:48No data—
Sun 18 OctHoensbroek 12:50Partial coverage+2 min+3 min
Sat 17 OctHoensbroek 12:48No data—
Fri 16 OctHoensbroek 12:48No data—
Thu 15 OctHoensbroek 12:48No data—
Tue 13 OctHoensbroek 12:48No data—
Mon 12 OctHoensbroek 12:48No data—
Sun 11 OctHoensbroek 12:49Partial coverage+1 min—
Sat 10 OctHoensbroek 12:48Partial coverage0 min—
Fri 9 OctHoensbroek 12:49Partial coverage+1 min+1 min
Thu 8 OctHoensbroek 12:50Partial coverage+2 min+3 min
Wed 7 OctHoensbroek 12:48Partial coverage0 min—