Train NS 3959 Sittard – Heerlen

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

It has not run yet today

Last recorded run: Saturday 14 November +1 min

Next service: today 18:26 from Sittard · Sun 15 Nov

Next departure 18:26 today · Sittard
On-time · 30 days
88%
22/25 runs under 3 min
RT coverage: 24 full · 1 partial · 4 no data
On-time · 90 days
91%
32/35 runs under 3 min
RT coverage: 34 full · 1 partial · 51 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Sun 18 Oct Max en route +5 min · last fix heading to Eindhoven Centraal +4 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Sittard +4 min
  • Sat 31 Oct Max en route +4 min · last fix heading to Sittard +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 75% F n=4
  • 83% S n=6
  • 75% S n=4

Stops and timetable

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

Last 90 days, 35 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:26on time on time
18: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
Sat 14 NovSittard 18:43Partial coverage+1 min+1 min
Fri 13 NovSittard 18:39+2 min+2 min
Thu 12 NovRoermond 18:44+1 min—
Wed 11 NovRoermond 18:44+1 min—
Tue 10 NovRoermond 18:44+2 min+2 min
Mon 9 NovRoermond 18:430 min+1 min
Sun 8 NovVlissingen Souburg 19:190 min—
Sat 7 NovVlissingen Souburg 19:190 min—
Fri 6 NovSittard 18:44+2 min+2 min
Thu 5 NovRoermond 18:440 min—
Wed 4 NovRoermond 18:440 min—
Tue 3 NovRoermond 18:240 min—
Mon 2 NovRoermond 18:49+3 min+3 min
Sun 1 NovSittard 18:430 min—
Sat 31 OctSittard 18:50+3 min+4 min
Fri 30 OctSittard 18:46No data—
Thu 29 OctWeert 18:090 min—
Wed 28 OctRoermond 18:42+1 min—
Tue 27 OctWeert 18:09No data—
Mon 26 OctWeert 19:01+3 min+3 min
Sun 25 OctSittard 18:45No data—
Sat 24 OctSittard 18:57+2 min+2 min
Fri 23 OctSittard 18:46+4 min+5 min
Thu 22 OctSittard 18:400 min—
Wed 21 OctSittard 18:45No data—
Tue 20 OctSittard 18:450 min—
Mon 19 OctSittard 18:450 min—
Sun 18 OctEindhoven Centraal 18:49+4 min+5 min
Sat 17 OctSittard 18:430 min—
Fri 16 OctSittard 18:44No data—