Train NS 3911 Sittard – Heerlen

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

✓ Today’s run finished

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

  1. Sittard06:26
  2. Heerlen06:41

Next service: tomorrow 06:26 from Sittard · Fri 6 Nov

Next departure 06:26 tomorrow · Sittard
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 0 full · 19 partial · 3 no data
On-time · 90 days
85%
17/20 runs under 3 min
RT coverage: 0 full · 20 partial · 43 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: +3 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

  • Wed 28 Oct Max en route +7 min · last fix heading to Sittard +7 min
  • Fri 30 Oct Max en route +6 min · last fix heading to Sittard +6 min
  • Tue 6 Oct Max en route +3 min · last fix heading to Sittard +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 17
  • 3–10 min 15% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 80% T n=5
  • 75% W n=4
  • 100% T n=4
  • 75% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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
06:26on time on time
06: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
Thu 5 NovSittard 06:44No data—
Wed 4 NovSittard 06:43Partial coverageNo data—
Tue 3 NovSittard 06:39Partial coverage+2 min+2 min
Mon 2 Nov— 06:43No data—
Fri 30 OctSittard 06:46Partial coverage+6 min+6 min
Thu 29 OctSittard 06:42Partial coverage0 min—
Wed 28 OctSittard 06:49Partial coverage+7 min+7 min
Tue 27 OctSittard 06:43Partial coverage+2 min+2 min
Mon 26 OctSittard 06:44Partial coverage+1 min+1 min
Fri 23 OctSittard 06:45Partial coverage+1 min+2 min
Thu 22 OctSittard 06:42Partial coverage+1 min+1 min
Wed 21 OctSittard 06:42Partial coverage0 min—
Tue 20 OctSittard 06:42Partial coverage0 min—
Mon 19 OctSittard 06:41Partial coverage0 min—
Fri 16 OctSittard 06:42Partial coverage0 min+1 min
Thu 15 OctSittard 06:45Partial coverage+2 min+2 min
Wed 14 OctSittard 06:44Partial coverage+1 min+1 min
Tue 13 OctSittard 06:46Partial coverage+2 min+2 min
Mon 12 OctSittard 06:46Partial coverage+2 min+2 min
Fri 9 OctSittard 06:40Partial coverage+1 min+1 min
Thu 8 OctSittard 06:43Partial coverage0 min—
Wed 7 OctSittard 06:40Partial coverage0 min—
Tue 6 OctSittard 06:45Partial coverage+3 min+3 min
Mon 5 OctSittard 06:51No data—
Fri 2 OctSittard 06:41No data—
Thu 1 OctSittard 06:40No data—
Wed 30 SeptSittard 06:40No data—
Tue 29 SeptSittard 06:40No data—
Mon 28 SeptSittard 06:40No data—
Fri 25 SeptSittard 06:40No data—