Train NS 3931 Sittard – Heerlen

Sittard 11:26 → Heerlen 11:41 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:26 from Sittard · Sun 15 Nov

Next departure 11:26 today · Sittard
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 20 full · 1 partial · 8 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 28 full · 1 partial · 57 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: +1 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 13 Nov Max en route +3 min · last fix heading to Sittard +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 75% F n=4
  • 100% 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, 29 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:26on time on time
11: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 NovSittard 11:42Partial coverage0 min—
Fri 13 NovSittard 11:39+3 min+3 min
Thu 12 NovSittard 11:430 min—
Wed 11 NovSittard 11:480 min—
Tue 10 NovSittard 11:44+2 min+2 min
Mon 9 NovSittard 11:43+1 min+4 min
Sun 8 NovVlissingen Souburg 12:190 min—
Sat 7 NovVlissingen Souburg 12:19+1 min+1 min
Fri 6 NovSittard 11:44No data—
Thu 5 NovSittard 11:42No data—
Wed 4 NovSittard 11:390 min—
Tue 3 NovSittard 11:42No data—
Mon 2 NovSittard 11:54No data—
Sun 1 NovSittard 11:43+1 min—
Sat 31 OctSittard 11:400 min—
Fri 30 OctSittard 11:410 min—
Thu 29 OctSittard 11:400 min—
Wed 28 OctSittard 11:420 min—
Tue 27 OctSittard 11:410 min—
Mon 26 OctSittard 11:40No data—
Sun 25 OctEindhoven Centraal 11:42No data—
Sat 24 OctSittard 11:440 min+1 min
Fri 23 OctSittard 11:440 min—
Thu 22 OctSittard 11:490 min—
Wed 21 OctSittard 11:43No data—
Tue 20 OctSittard 11:450 min—
Mon 19 OctSittard 11:460 min—
Sun 18 OctEindhoven Centraal 11:420 min—
Sat 17 OctEindhoven Centraal 11:43No data—
Fri 16 OctSittard 11:45No data—