Train NS 3928 Heerlen – Sittard

Heerlen 07:49 → Sittard 08:04 Mon, Tue, Wed, Thu, Sun 0 h 15 min · 2 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Heerlen at 08:04 0 min

  1. Heerlen07:49
  2. Sittard08:04

Next service: tomorrow 07:49 from Heerlen · Mon 16 Nov

Next departure 07:49 tomorrow · Heerlen
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 17 full · 1 partial · 6 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 22 full · 1 partial · 42 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Sittard, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 6 Oct Max en route +10 min · last fix heading to Bovenkarspel Flora +8 min
  • Thu 12 Nov Max en route +8 min · last fix heading to Bovenkarspel Flora +8 min
  • Wed 11 Nov Max en route +6 min · last fix heading to Bovenkarspel Flora +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 20
  • 3–10 min 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 67% T n=3
  • 83% W n=6
  • 75% T n=4
  • 100% F n=1
  • 100% S n=2
  • 100% S n=5

Stops and timetable

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

Last 90 days, 23 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
07:49on time on time
08:04on time +5 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
Sun 15 NovHeerlen 08:04Partial coverage0 min+1 min
Thu 12 NovBovenkarspel Flora 11:39+8 min+8 min
Wed 11 NovBovenkarspel Flora 11:34+6 min+6 min
Tue 10 NovBovenkarspel Flora 11:340 min—
Mon 9 NovBovenkarspel Flora 11:340 min—
Sun 8 NovBovenkarspel Flora 11:340 min—
Sat 7 NovBovenkarspel Flora 11:340 min—
Thu 5 NovBovenkarspel Flora 11:34No data—
Wed 4 NovBovenkarspel Flora 11:34+1 min—
Tue 3 NovBovenkarspel Flora 11:35No data—
Mon 2 NovBovenkarspel Flora 11:33No data—
Sun 1 NovHeerlen 08:070 min+1 min
Thu 29 OctBovenkarspel Flora 11:340 min—
Wed 28 OctBovenkarspel Flora 11:340 min—
Tue 27 OctBovenkarspel Flora 11:340 min—
Mon 26 OctBovenkarspel Flora 11:340 min—
Sun 25 OctHeerlen 08:05No data—
Sat 24 OctBovenkarspel Flora 11:340 min—
Fri 23 OctBovenkarspel Flora 11:430 min—
Thu 22 OctBovenkarspel Flora 11:340 min—
Wed 21 OctBovenkarspel Flora 11:340 min—
Tue 20 OctBovenkarspel Flora 11:34No data—
Mon 19 OctBovenkarspel Flora 11:34No data—
Sun 18 OctHeerlen 08:080 min—
Thu 15 OctBovenkarspel Flora 11:43No data—
Wed 14 OctBovenkarspel Flora 11:340 min—
Tue 13 OctBovenkarspel Flora 11:34No data—
Mon 12 OctBovenkarspel Flora 11:33No data—
Sun 11 OctHeerlen 08:05+1 min+1 min
Thu 8 OctBovenkarspel Flora 11:34+1 min—