Train Arriva 32557 Sittard – Heerlen

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 15:48 from Sittard · Sun 8 Nov

Next departure 15:48 today · Sittard
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 0 full · 11 partial · 17 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 0 full · 15 partial · 72 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

  • Sun 11 Oct Max en route +8 min · last fix heading to Hoensbroek +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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