Train NS 13933 Eindhoven Centraal – Heerlen

Eindhoven Centraal 11:08 → Heerlen 12:11 Fri, Sat, Sun 1 h 03 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 8 November +2 min

Next service: today 11:08 from Eindhoven Centraal · Fri 13 Nov

Next departure 11:08 today · Eindhoven Centraal
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 2 full · 3 partial · 2 no data
On-time · 90 days
71%
5/7 runs under 3 min
RT coverage: 4 full · 3 partial · 15 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
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 +11 min · last fix heading to Sittard +11 min
  • Sat 10 Oct Max en route +7 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 5
  • 3–10 min 14% · 1
  • 10–30 min 14% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 50% F n=2
  • 75% S n=4
  • 100% S n=1

Stops and timetable

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

Last 90 days, 7 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
11:08on time on time
11:26— —
11:39 / 11:40— —
11:55 / 11:56— —
12:11— —

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 8 NovEindhoven Centraal 12:14Partial coverage+2 min+3 min
Sat 7 NovSittard 12:12Partial coverage0 min—
Fri 6 NovSittard 12:09No data—
Sat 31 OctSittard 12:11+2 min+2 min
Fri 30 OctSittard 12:10No data—
Sat 17 OctSittard 12:110 min—
Fri 16 OctSittard 12:13Partial coverage0 min—
Sat 10 OctSittard 12:16+4 min+7 min
Fri 9 OctSittard 12:20+11 min+11 min
Sat 3 OctSittard 12:10No data—
Fri 2 OctSittard 12:13No data—
Sat 26 SeptSittard 12:10No data—
Fri 25 SeptSittard 12:10No data—
Sat 19 SeptSittard 12:10No data—
Fri 18 SeptSittard 12:12No data—
Sat 12 SeptSittard 12:12No data—
Fri 11 SeptSittard 12:10No data—
Sat 5 SeptWeert 11:40No data—
Fri 4 SeptSittard 12:10No data—
Sat 29 AugSittard 12:13No data—
Fri 28 AugSittard 12:10No data—
Fri 21 AugSittard 12:10No data—