Train NS 3927 Sittard – Heerlen

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

✓ Today’s run finished

Today, last fix heading to Sittard at 10:43 +1 min

  1. Sittard10:26
  2. Heerlen10:41

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

Next departure 10:26 tomorrow · Sittard
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 26 full · 1 partial · 3 no data
On-time · 90 days
92%
34/37 runs under 3 min
RT coverage: 36 full · 1 partial · 50 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: +2 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 9 Oct Max en route +8 min · last fix heading to Sittard +7 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Roermond +4 min
  • Sat 10 Oct Max en route +7 min · last fix heading to Sittard +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 34
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 83% W n=6
  • 100% T n=5
  • 80% F n=5
  • 83% S n=6
  • 100% S n=4

Stops and timetable

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

Last 90 days, 37 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
10:26on time on time
10: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 10:43Partial coverage+1 min+1 min
Fri 13 NovSittard 10:39+1 min+1 min
Thu 12 NovSittard 10:44+3 min+4 min
Wed 11 NovSittard 10:440 min—
Tue 10 NovSittard 10:420 min+9 min
Mon 9 NovSittard 10:390 min—
Sun 8 NovVlissingen Souburg 11:19+1 min—
Sat 7 NovVlissingen Souburg 11:22+2 min+2 min
Fri 6 NovSittard 10:44No data—
Thu 5 NovSittard 10:43No data—
Wed 4 NovRoermond 10:24+4 min+4 min
Tue 3 NovSittard 10:540 min—
Mon 2 NovSittard 10:420 min—
Sun 1 NovSittard 10:450 min+2 min
Sat 31 OctSittard 10:46+1 min+3 min
Fri 30 OctSittard 10:400 min—
Thu 29 OctSittard 10:400 min—
Wed 28 OctSittard 10:450 min—
Tue 27 OctSittard 10:420 min—
Mon 26 OctSittard 10:410 min—
Sun 25 OctSittard 10:42No data—
Sat 24 OctSittard 10:46+2 min+3 min
Fri 23 OctSittard 10:460 min—
Thu 22 OctSittard 10:520 min—
Wed 21 OctSittard 10:440 min—
Tue 20 OctSittard 10:400 min—
Mon 19 OctSittard 10:440 min—
Sun 18 OctSittard 10:450 min+3 min
Sat 17 OctSittard 10:450 min—
Fri 16 OctSittard 10:430 min—