Train Arriva 32531 Sittard – Heerlen

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

✓ Today’s run finished

Today, last fix heading to Hoensbroek at 09:49 +4 min

  1. Sittard09:18
  2. Geleen Oost09:22
  3. Spaubeek09:25
  4. Schinnen09:27
  5. Nuth09:30
  6. Hoensbroek09:34
  7. Heerlen09:38

Next service: tomorrow 09:18 from Sittard · Tue 17 Nov

Next departure 09:18 tomorrow · Sittard
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 0 full · 18 partial · 12 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 0 full · 24 partial · 64 no data
Typical delay
0min
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

  • Mon 16 Nov Max en route +4 min · last fix heading to Hoensbroek +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 100% T n=4
  • 100% W n=3
  • 100% T n=2
  • 100% F n=2
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 24 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:18on time on time
09:22— —
09:25— —
09:27— —
09:30— —
09:34— —
09: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
Mon 16 NovHoensbroek 09:49Partial coverage+4 min+4 min
Sun 15 NovHoensbroek 09:48Partial coverage0 min—
Sat 14 NovHoensbroek 09:48Partial coverage0 min—
Fri 13 NovHoensbroek 09:49Partial coverage+1 min+2 min
Thu 12 NovHoensbroek 09:48Partial coverage0 min—
Wed 11 NovHoensbroek 09:49Partial coverage+1 min+1 min
Tue 10 NovHoensbroek 09:49Partial coverage+2 min+3 min
Mon 9 NovHoensbroek 09:49Partial coverage+1 min+1 min
Sun 8 NovHoensbroek 09:49Partial coverage+1 min—
Sat 7 NovHoensbroek 09:49Partial coverage+2 min+2 min
Fri 6 NovHoensbroek 09:49No data—
Thu 5 NovHoensbroek 09:54No data—
Wed 4 NovHoensbroek 09:49Partial coverage+2 min+3 min
Tue 3 NovHoensbroek 09:49No data—
Mon 2 NovHoensbroek 09:53No data—
Sun 1 NovHoensbroek 09:49Partial coverage+1 min—
Sat 31 OctHoensbroek 09:48Partial coverage0 min—
Fri 30 OctHoensbroek 09:53No data—
Thu 29 OctHoensbroek 09:49No data—
Wed 28 OctHoensbroek 09:49Partial coverage0 min—
Tue 27 OctHoensbroek 09:48Partial coverage0 min—
Mon 26 OctHoensbroek 09:49No data—
Sun 25 OctHoensbroek 09:49No data—
Sat 24 OctHoensbroek 09:48Partial coverage0 min—
Fri 23 OctHoensbroek 09:48No data—
Thu 22 OctHoensbroek 09:49No data—
Wed 21 OctHoensbroek 09:49No data—
Tue 20 OctHoensbroek 09:48Partial coverage0 min—
Mon 19 OctHoensbroek 09:49No data—
Sun 18 OctHoensbroek 09:48Partial coverage0 min—