Train Arriva 32525 Sittard – Heerlen

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

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 07:48 from Sittard · Wed 18 Nov

Next departure 07:48 today · Sittard
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 0 full · 21 partial · 8 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 0 full · 29 partial · 58 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 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

Worst days

  • Tue 6 Oct Max en route +13 min · last fix heading to Hoensbroek +12 min
  • Mon 16 Nov Max en route +6 min · last fix heading to Hoensbroek +6 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Hoensbroek +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 26
  • 3–10 min 7% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 67% T n=6
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=6
  • 100% S n=4

Stops and timetable

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

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