Train NS 3983 Sittard – Heerlen

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

✓ Today’s run finished

Today, last fix heading to — at 00:49 0 min

  1. Sittard00:26
  2. Heerlen00:41

Next service: tomorrow 00:26 from Sittard · Sun 15 Nov

Next departure 00:26 tomorrow · Sittard
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 22 full · 0 partial · 4 no data
On-time · 90 days
90%
28/31 runs under 3 min
RT coverage: 31 full · 0 partial · 11 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: +4 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

  • Fri 30 Oct Max en route +7 min · last fix heading to — +7 min
  • Thu 12 Nov Max en route +5 min · last fix heading to — +5 min
  • Thu 5 Nov Max en route +4 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 90% · 28
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=6
  • 67% T n=6
  • 67% F n=3
  • 100% S n=5
  • 100% S n=3

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
00:26on time on time
00:41on 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 Nov— 00:490 min—
Fri 13 Nov— 00:44+1 min+2 min
Thu 12 Nov— 00:49+5 min+5 min
Wed 11 Nov— 00:430 min+1 min
Tue 10 Nov— 00:42+1 min+1 min
Sun 8 NovVlissingen Souburg 01:190 min—
Sat 7 Nov— 00:43+1 min+1 min
Fri 6 Nov— 00:43No data—
Thu 5 Nov— 00:49+4 min+4 min
Wed 4 Nov— 00:440 min—
Mon 2 NovSittard 00:390 min—
Sun 1 Nov— 00:43No data—
Fri 30 Oct— 00:56+7 min+7 min
Thu 29 Oct— 00:420 min—
Wed 28 Oct— 00:430 min—
Tue 27 Oct— 00:450 min—
Mon 26 OctSittard 00:43No data—
Sat 24 OctAmsterdam Amstel 00:510 min—
Fri 23 Oct— 00:54No data—
Thu 22 Oct— 00:480 min—
Wed 21 Oct— 00:450 min—
Tue 20 Oct— 00:430 min—
Mon 19 OctSittard 00:45+1 min+1 min
Sun 18 OctSittard 00:450 min—
Sat 17 Oct— 00:46+2 min+2 min
Fri 16 Oct— 00:430 min—
Thu 15 Oct— 00:420 min—
Wed 14 Oct— 00:420 min—
Tue 13 Oct— 00:420 min—
Mon 12 OctSittard 00:430 min—