Train NS 13940 Heerlen – Sittard

Heerlen 10:49 → Sittard 11:04 Fri, Sat, Sun 0 h 15 min · 2 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Sunday 15 November 0 min

Next service: Friday 10:49 from Heerlen · Fri 20 Nov

Next departure 10:49 Friday · Heerlen
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 7 full · 2 partial · 2 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 12 full · 2 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Sun 18 Oct Max en route +4 min · last fix heading to Weert +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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:49on time on time
11:04on time +1 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 11:05Partial coverage0 min—
Sat 14 NovHeerlen 11:04Partial coverage+1 min+1 min
Fri 13 NovWeert 11:520 min—
Sun 8 NovWeert 11:580 min—
Sat 7 NovWeert 11:520 min—
Fri 6 NovWeert 12:28No data—
Sun 1 NovWeert 12:02+1 min+1 min
Sat 31 OctWeert 11:520 min—
Fri 30 OctWeert 11:520 min—
Sun 25 OctWeert 11:53No data—
Sun 18 OctWeert 14:23+4 min+4 min
Sat 17 OctWeert 12:010 min—
Fri 16 OctWeert 11:520 min—
Sun 11 OctWeert 11:55+1 min+1 min
Sat 10 OctWeert 12:010 min—
Fri 9 OctWeert 12:04+1 min+1 min
Sun 4 OctWeert 11:49No data—
Sat 3 OctWeert 11:48No data—
Fri 2 OctWeert 11:52No data—
Sun 27 SeptWeert 11:49No data—
Sat 26 SeptWeert 11:48No data—
Fri 25 SeptWeert 11:49No data—
Sun 20 SeptWeert 11:49No data—
Sat 19 SeptWeert 11:49No data—
Fri 18 SeptWeert 11:50No data—
Sun 13 SeptWeert 11:49No data—
Sat 12 SeptWeert 11:49No data—
Fri 11 SeptWeert 11:49No data—
Sun 6 SeptWeert 11:50No data—
Sat 5 SeptWeert 11:50No data—