Train NS 3942 Heerlen – Sittard

Heerlen 11:19 → Sittard 11:34 Daily 0 h 15 min · 2 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 11:19 from Heerlen · Sun 15 Nov

Next departure 11:19 today · Heerlen
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 22 full · 1 partial · 6 no data
On-time · 90 days
91%
30/33 runs under 3 min
RT coverage: 32 full · 1 partial · 53 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 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

  • Wed 4 Nov Max en route +19 min · last fix heading to Bovenkarspel Flora +19 min
  • Sat 7 Nov Max en route +13 min · last fix heading to Bovenkarspel Flora +11 min
  • Tue 6 Oct Max en route +10 min · last fix heading to Bovenkarspel Flora +10 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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
11:19on time on time
11:34on time +2 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 NovHeerlen 11:34Partial coverage0 min—
Fri 13 NovWeert 12:190 min—
Thu 12 NovBovenkarspel Flora 15:040 min—
Wed 11 NovBovenkarspel Flora 15:040 min—
Tue 10 NovBovenkarspel Flora 15:040 min—
Mon 9 NovBovenkarspel Flora 15:04+3 min+3 min
Sun 8 NovBovenkarspel Flora 15:040 min—
Sat 7 NovBovenkarspel Flora 15:14+11 min+13 min
Fri 6 NovWeert 12:34No data—
Thu 5 NovBovenkarspel Flora 15:040 min—
Wed 4 NovBovenkarspel Flora 15:04+19 min+19 min
Tue 3 NovBovenkarspel Flora 15:04No data—
Mon 2 NovBovenkarspel Flora 15:040 min—
Sun 1 NovWeert 12:200 min—
Sat 31 OctWeert 12:220 min—
Fri 30 OctWeert 12:220 min—
Thu 29 OctBovenkarspel Flora 15:040 min—
Wed 28 OctBovenkarspel Flora 15:040 min—
Tue 27 OctBovenkarspel Flora 15:040 min—
Mon 26 OctBovenkarspel Flora 15:03No data—
Sun 25 OctWeert 12:22No data—
Sat 24 OctBovenkarspel Flora 15:04+1 min+2 min
Fri 23 OctBovenkarspel Flora 15:05No data—
Thu 22 OctBovenkarspel Flora 15:030 min—
Wed 21 OctBovenkarspel Flora 15:040 min—
Tue 20 OctBovenkarspel Flora 15:040 min—
Mon 19 OctBovenkarspel Flora 15:030 min—
Sun 18 OctWeert 12:220 min—
Sat 17 OctWeert 12:22No data—
Fri 16 OctWeert 12:220 min—