Train Arriva 32559 Sittard – Heerlen

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

✓ Today’s run finished

Today, last fix heading to Hoensbroek at 16:48 No data

  1. Sittard16:18
  2. Geleen Oost16:22
  3. Spaubeek16:25
  4. Schinnen16:27
  5. Nuth16:30
  6. Hoensbroek16:34
  7. Heerlen16:38

Next service: tomorrow 16:18 from Sittard · Fri 6 Nov

Next departure 16:18 tomorrow · Sittard
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 0 full · 14 partial · 15 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 0 full · 16 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sat 31 Oct Max en route +15 min · last fix heading to Hoensbroek +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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