Train Arriva 32564 Heerlen – Sittard

Heerlen 18:22 → Sittard 18:42 Daily 0 h 20 min · 7 stops Arriva

✓ Today’s run finished

Today, last fix heading to Geleen Oost at 18:53 0 min

  1. Heerlen18:22
  2. Hoensbroek18:26
  3. Nuth18:29
  4. Schinnen18:32
  5. Spaubeek18:34
  6. Geleen Oost18:38
  7. Sittard18:42

Next service: tomorrow 18:22 from Heerlen · Sun 8 Nov

Next departure 18:22 tomorrow · Heerlen
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 0 full · 11 partial · 10 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 0 full · 11 partial · 47 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 Sittard, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 23 Oct Max en route +8 min · last fix heading to Geleen Oost +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 10
  • 3–10 min 9% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=1
  • — W n=0
  • — T n=0
  • 67% F n=3
  • 100% 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, 11 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
18:22on time +1 min
18:26— —
18:29— —
18:32— —
18:34— —
18:38— —
18:42— —

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 NovGeleen Oost 18:53Partial coverage0 min—
Fri 6 NovGeleen Oost 18:52Partial coverage+1 min+1 min
Sun 1 NovGeleen Oost 18:52Partial coverage0 min—
Sat 31 OctGeleen Oost 18:52Partial coverage0 min—
Fri 30 OctGeleen Oost 18:52No data—
Sun 25 OctGeleen Oost 18:59No data—
Sat 24 OctGeleen Oost 19:06No data—
Fri 23 OctGeleen Oost 18:52Partial coverage+8 min+8 min
Thu 22 OctGeleen Oost 18:52No data—
Wed 21 OctGeleen Oost 18:52No data—
Tue 20 OctGeleen Oost 18:50Partial coverage0 min—
Mon 19 OctGeleen Oost 18:52No data—
Sun 18 OctGeleen Oost 18:53Partial coverage0 min+1 min
Sat 17 OctGeleen Oost 18:52No data—
Fri 16 OctGeleen Oost 18:52No data—
Thu 15 OctNuth 18:43No data—
Tue 13 OctGeleen Oost 18:50No data—
Mon 12 OctGeleen Oost 18:52Partial coverage0 min—
Sun 11 OctGeleen Oost 18:53Partial coverage0 min—
Sat 10 OctGeleen Oost 18:52Partial coverage0 min—
Fri 9 OctSpaubeek 18:48Partial coverage+1 min+1 min
Sun 4 OctGeleen Oost 18:59No data—
Sat 3 OctGeleen Oost 18:52No data—
Fri 2 OctGeleen Oost 18:52No data—
Sun 27 SeptGeleen Oost 18:52No data—
Sat 26 SeptGeleen Oost 18:53No data—
Fri 25 SeptSpaubeek 18:48No data—
Sun 20 SeptGeleen Oost 18:52No data—
Sat 19 SeptGeleen Oost 18:52No data—
Fri 18 SeptGeleen Oost 18:52No data—