Train NS 3984 Heerlen – Sittard

Heerlen 21:49 → Sittard 22:04 Daily 0 h 15 min · 2 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 21:49 from Heerlen · Sat 7 Nov

Next departure 21:49 today · Heerlen
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 9 full · 5 partial · 14 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 12 full · 5 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 12% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • — T n=0
  • 100% W n=2
  • 50% T n=2
  • 75% F n=4
  • 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, 17 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
21:49on time on time
22:04on time +4 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
Fri 6 Nov— 22:040 min—
Thu 5 Nov— 22:04No data—
Wed 4 Nov— 22:080 min+1 min
Mon 2 Nov— 22:040 min—
Sun 1 NovHeerlen 22:04Partial coverage0 min—
Sat 31 OctHeerlen 22:05Partial coverage0 min—
Fri 30 Oct— 22:05No data—
Thu 29 Oct— 22:050 min—
Wed 28 Oct— 22:05No data—
Tue 27 Oct— 22:06No data—
Mon 26 Oct— 22:050 min—
Sun 25 OctHeerlen 22:12No data—
Sat 24 OctWeert 01:250 min—
Fri 23 Oct— 22:20+7 min+7 min
Thu 22 Oct— 22:10No data—
Wed 21 Oct— 22:06No data—
Tue 20 Oct— 22:06No data—
Mon 19 Oct— 22:05No data—
Sun 18 OctHeerlen 22:05Partial coverage0 min—
Sat 17 OctHeerlen 22:08No data—
Fri 16 Oct— 22:050 min—
Thu 15 Oct— 22:07No data—
Wed 14 Oct— 22:05No data—
Tue 13 Oct— 22:06No data—
Mon 12 Oct— 22:05No data—
Sun 11 OctHeerlen 22:05Partial coverage0 min+1 min
Sat 10 OctHeerlen 22:10Partial coverage+2 min+3 min
Fri 9 Oct— 22:070 min+1 min
Thu 8 Oct— 22:12+4 min+4 min
Wed 7 Oct— 22:050 min+1 min