Train NS 3975 Sittard – Heerlen

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

It has not run yet today

Last recorded run: Thursday 19 November +3 min

Next service: today 22:26 from Sittard · Fri 20 Nov

Next departure 22:26 today · Sittard
On-time · 30 days
71%
15/21 runs under 3 min
RT coverage: 20 full · 1 partial · 7 no data
On-time · 90 days
74%
23/31 runs under 3 min
RT coverage: 30 full · 1 partial · 25 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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 7 Nov Max en route +13 min · last fix heading to Vlissingen Souburg +10 min
  • Fri 13 Nov Max en route +6 min · last fix heading to — +6 min
  • Wed 18 Nov Max en route +5 min · last fix heading to — +5 min
  • Thu 8 Oct Max en route +5 min · last fix heading to — +5 min
  • Tue 10 Nov Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 74% · 23
  • 3–10 min 26% · 8
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 67% T n=3
  • 75% W n=4
  • 50% T n=4
  • 40% F n=5
  • 80% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 31 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
22:26on time +1 min
22:41+2 min +5 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 19 Nov— 22:44+3 min+3 min
Wed 18 Nov— 22:44+5 min+5 min
Tue 17 Nov— 22:43+2 min+2 min
Mon 16 Nov— 22:44+2 min+2 min
Sun 15 NovSittard 22:440 min+1 min
Sat 14 NovSittard 22:44+2 min+2 min
Fri 13 Nov— 22:44+6 min+6 min
Thu 12 Nov— 22:44+1 min—
Wed 11 Nov— 22:43+1 min—
Tue 10 Nov— 22:44+4 min+5 min
Mon 9 Nov— 22:420 min+1 min
Sun 8 NovVlissingen Souburg 23:19+1 min+1 min
Sat 7 NovVlissingen Souburg 23:19+10 min+13 min
Fri 6 Nov— 22:44+4 min+4 min
Thu 5 Nov— 22:44No data—
Wed 4 Nov— 22:44+1 min+2 min
Mon 2 Nov— 22:420 min+1 min
Sun 1 NovSittard 22:43+2 min+2 min
Sat 31 OctSittard 22:42Partial coverage0 min—
Fri 30 Oct— 22:42No data—
Thu 29 Oct— 22:46+1 min+1 min
Wed 28 Oct— 22:46No data—
Tue 27 Oct— 22:44No data—
Mon 26 Oct— 22:44No data—
Sun 25 OctSittard 22:46No data—
Sat 24 OctSittard 22:450 min—
Fri 23 Oct— 22:47+2 min+2 min
Thu 22 Oct— 22:47No data—
Wed 21 Oct— 22:46No data—
Tue 20 Oct— 22:46No data—