Train NS 3979 Sittard – Heerlen

Sittard 23:26 → Heerlen 23:41 Daily 0 h 15 min · 2 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 23:26 from Sittard · Fri 6 Nov

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

  • Thu 29 Oct Max en route +7 min · last fix heading to — +7 min
  • Fri 16 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=3
  • 50% T n=2
  • 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 (2 stops).

Last 90 days, 18 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
23:26on time +3 min
23:41+1 min +3 min

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 Nov— 23:44No data—
Wed 4 Nov— 23:44+2 min+2 min
Mon 2 Nov— 23:44+2 min+2 min
Sun 1 NovSittard 23:42Partial coverage0 min—
Sat 31 Oct— 23:430 min—
Fri 30 Oct— 23:44No data—
Thu 29 Oct— 23:49+7 min+7 min
Wed 28 Oct— 23:45No data—
Tue 27 Oct— 23:45No data—
Mon 26 Oct— 23:45No data—
Sun 25 OctSittard 23:45No data—
Sat 24 OctEindhoven Centraal 23:450 min—
Fri 23 Oct— 23:45+2 min+2 min
Thu 22 Oct— 23:46No data—
Wed 21 Oct— 23:45No data—
Tue 20 Oct— 23:42No data—
Mon 19 Oct— 23:43No data—
Sun 18 OctSittard 23:42Partial coverage0 min—
Sat 17 OctSittard 23:45No data—
Fri 16 Oct— 23:51+4 min+4 min
Thu 15 Oct— 23:49No data—
Wed 14 Oct— 23:430 min—
Tue 13 Oct— 23:42No data—
Mon 12 Oct— 23:43+1 min—
Sun 11 OctSittard 23:45Partial coverage0 min—
Sat 10 Oct— 23:430 min+1 min
Fri 9 Oct— 23:46+2 min+2 min
Thu 8 Oct— 23:420 min—
Wed 7 Oct— 23:45+1 min+1 min
Tue 6 Oct— 23:420 min+1 min