Train Arriva 32533 Sittard – Heerlen

Sittard 09:48 → Heerlen 10:08 Daily 0 h 20 min · 7 stops Arriva

✓ Today’s run finished

Today, last fix heading to Hoensbroek at 10:18 No data

  1. Sittard09:48
  2. Geleen Oost09:52
  3. Spaubeek09:55
  4. Schinnen09:57
  5. Nuth10:00
  6. Hoensbroek10:04
  7. Heerlen10:08

Next service: tomorrow 09:48 from Sittard · Sat 7 Nov

Next departure 09:48 tomorrow · Sittard
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 18 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 75 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

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

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

On-time by weekday

  • — M n=0
  • 100% T n=2
  • 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, 12 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
09:48on time on time
09:52— —
09:55— —
09:57— —
10:00— —
10:04— —
10:08— —

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 10:18No data—
Thu 5 NovHoensbroek 10:19No data—
Tue 3 NovHoensbroek 10:19No data—
Mon 2 NovHoensbroek 10:18No data—
Sun 1 NovHoensbroek 10:20Partial coverage+2 min+2 min
Sat 31 OctHoensbroek 10:19Partial coverage+1 min—
Fri 30 OctHoensbroek 10:26No data—
Thu 29 OctHoensbroek 10:19No data—
Wed 28 OctHoensbroek 10:18Partial coverage0 min—
Tue 27 OctHoensbroek 10:19No data—
Mon 26 OctHoensbroek 10:18No data—
Sun 25 OctHoensbroek 10:20No data—
Sat 24 OctHoensbroek 10:20Partial coverage+2 min+3 min
Fri 23 OctHoensbroek 10:18No data—
Thu 22 OctHoensbroek 10:19No data—
Wed 21 OctHoensbroek 10:18No data—
Tue 20 OctHoensbroek 10:18Partial coverage0 min—
Mon 19 OctHoensbroek 10:21No data—
Sun 18 OctHoensbroek 10:20Partial coverage+1 min+1 min
Sat 17 OctHoensbroek 10:18Partial coverage0 min—
Fri 16 OctHoensbroek 10:18No data—
Thu 15 OctHoensbroek 10:18No data—
Tue 13 OctHoensbroek 10:20No data—
Mon 12 OctHoensbroek 10:21No data—
Sun 11 OctHoensbroek 10:19Partial coverage+1 min+1 min
Sat 10 OctHoensbroek 10:18No data—
Fri 9 OctHoensbroek 10:21Partial coverage+3 min+3 min
Thu 8 OctHoensbroek 10:19Partial coverage0 min—
Wed 7 OctHoensbroek 10:19Partial coverage0 min—
Tue 6 OctHoensbroek 10:18Partial coverage0 min—