Train Arriva 32577 Sittard – Heerlen

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

✓ Today’s run finished

Today, last fix heading to Hoensbroek at 21:19 +1 min

  1. Sittard20:48
  2. Geleen Oost20:52
  3. Spaubeek20:55
  4. Schinnen20:57
  5. Nuth21:00
  6. Hoensbroek21:04
  7. Heerlen21:08

Next service: tomorrow 20:48 from Sittard · Mon 16 Nov

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

Distribution · 90 days

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=2
  • 100% S n=5

Stops and timetable

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

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