Train Arriva 32521 Sittard – Heerlen

Sittard 06:48 → Heerlen 07:08 Mon, Tue, Wed, Thu, Fri, Sat 0 h 20 min · 7 stops Arriva

✓ Today’s run finished

Today, last fix heading to Hoensbroek at 07:54 No data

  1. Sittard06:48
  2. Geleen Oost06:52
  3. Spaubeek06:55
  4. Schinnen06:57
  5. Nuth07:00
  6. Hoensbroek07:04
  7. Heerlen07:08

Next service: tomorrow 06:48 from Sittard · Fri 6 Nov

Next departure 06:48 tomorrow · Sittard
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 0 full · 21 partial · 3 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 0 full · 22 partial · 52 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Wed 28 Oct Max en route +11 min · last fix heading to Hoensbroek +11 min
  • Fri 30 Oct Max en route +4 min · last fix heading to Hoensbroek +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 67% W n=3
  • 100% T n=3
  • 75% F n=4
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
06:48on time on time
06:52— —
06:55— —
06:57— —
07:00— —
07:04— —
07: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
Thu 5 NovHoensbroek 07:54No data—
Wed 4 NovHoensbroek 07:18Partial coverageNo data—
Tue 3 NovHoensbroek 07:19Partial coverage+2 min+3 min
Sat 31 OctHoensbroek 07:19Partial coverage+1 min—
Fri 30 OctHoensbroek 07:22Partial coverage+4 min+4 min
Thu 29 OctHoensbroek 07:18Partial coverage+1 min—
Wed 28 OctHoensbroek 07:29Partial coverage+11 min+11 min
Tue 27 OctHoensbroek 07:19Partial coverage+1 min+1 min
Mon 26 OctHoensbroek 07:19Partial coverage+1 min—
Sat 24 OctHoensbroek 07:20Partial coverage+3 min+4 min
Fri 23 OctHoensbroek 07:19Partial coverage+1 min—
Thu 22 OctHoensbroek 07:18Partial coverageNo data—
Wed 21 OctHoensbroek 07:18Partial coverage0 min—
Tue 20 OctHoensbroek 07:18Partial coverage+1 min—
Mon 19 OctHoensbroek 07:19Partial coverage+1 min+2 min
Sat 17 OctHoensbroek 07:18Partial coverage0 min—
Fri 16 OctHoensbroek 07:18Partial coverage0 min—
Thu 15 OctHoensbroek 07:19Partial coverage+1 min+1 min
Tue 13 OctHoensbroek 07:19Partial coverage+1 min+1 min
Mon 12 OctHoensbroek 07:19Partial coverage+1 min—
Sat 10 OctHoensbroek 07:18Partial coverage0 min—
Fri 9 OctHoensbroek 07:20Partial coverage+2 min+2 min
Thu 8 OctHoensbroek 07:20Partial coverage+2 min+3 min
Wed 7 OctHoensbroek 07:18Partial coverage0 min—
Tue 6 OctHoensbroek 07:19Partial coverage+1 min—
Mon 5 OctHoensbroek 07:19No data—
Sat 3 OctHoensbroek 07:18No data—
Fri 2 OctHoensbroek 07:20No data—
Thu 1 OctHoensbroek 07:19No data—
Wed 30 SeptHoensbroek 07:19No data—