Train NS 3915 Sittard – Heerlen

Sittard 07:26 → Heerlen 07:41 Mon, Tue, Wed, Thu, Fri, Sat 0 h 15 min · 2 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Sittard at 07:44 No data

  1. Sittard07:26
  2. Heerlen07:41

Next service: tomorrow 07:26 from Sittard · Sat 7 Nov

Full trip card
Next departure 07:26 tomorrow · Sittard
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 0 full · 14 partial · 12 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 0 full · 16 partial · 59 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: +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 +5 min · last fix heading to Sittard +5 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=4
  • 100% T n=2
  • 33% F n=3
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 16 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
Sittard
07:26on time on time
Heerlen
07:41— —

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 NovSittard 07:44No data—
Thu 5 NovSittard 08:04No data—
Wed 4 NovSittard 07:43Partial coverageNo data—
Tue 3 NovSittard 07:39No data—
Mon 2 NovSittard 07:44No data—
Sat 31 OctSittard 07:45Partial coverage+1 min+2 min
Fri 30 OctSittard 07:42Partial coverage+5 min+5 min
Thu 29 OctSittard 07:42Partial coverage+3 min+3 min
Wed 28 OctSittard 07:47Partial coverage0 min—
Tue 27 OctSittard 07:47Partial coverage0 min—
Mon 26 OctSittard 07:44Partial coverage+2 min+2 min
Sat 24 OctSittard 07:43Partial coverage+1 min+1 min
Fri 23 OctSittard 07:46Partial coverage+1 min+2 min
Thu 22 OctSittard 07:43No data—
Wed 21 OctSittard 07:43Partial coverage0 min—
Tue 20 OctSittard 07:40No data—
Mon 19 OctSittard 07:43No data—
Sat 17 OctSittard 07:46Partial coverage+2 min+2 min
Fri 16 OctSittard 07:45No data—
Thu 15 OctSittard 07:47No data—
Wed 14 OctSittard 07:40Partial coverage0 min—
Tue 13 OctSittard 07:44No data—
Mon 12 OctSittard 07:46No data—
Sat 10 OctSittard 07:43Partial coverage0 min+1 min
Fri 9 OctSittard 07:46Partial coverage+4 min+4 min
Thu 8 OctSittard 07:45Partial coverage+2 min+2 min
Wed 7 OctSittard 07:43Partial coverage0 min+1 min
Tue 6 OctSittard 07:42Partial coverage0 min+1 min
Mon 5 OctSittard 07:41No data—
Sat 3 OctSittard 07:40No data—