Train NS 13944 Heerlen – Eindhoven Centraal

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

It does not run today

Last recorded run: Sunday 8 November 0 min

Next service: tomorrow 11:49 from Heerlen · Fri 13 Nov

Next departure 11:49 tomorrow · Heerlen
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 6 full · 1 partial · 3 no data
On-time · 90 days
90%
9/10 runs under 3 min
RT coverage: 9 full · 1 partial · 24 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 Eindhoven Centraal, in minutes. One bar per run.

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

Worst days

  • Sat 10 Oct Max en route +6 min · last fix heading to Weert +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 9
  • 3–10 min 10% · 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=2
  • 75% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 10 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:49on time on time
12:04 / 12:05≈ on time ≈ +1 min
12:19 / 12:20≈ on time ≈ +1 min
12:36≈ on time ≈ +2 min
12:56on time +3 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 8 NovWeert 12:57Partial coverage0 min—
Sat 7 NovWeert 12:520 min—
Fri 6 NovWeert 12:59No data—
Sun 1 NovWeert 12:490 min—
Sat 31 OctWeert 13:02+1 min+2 min
Fri 30 OctWeert 12:520 min—
Sun 25 OctSittard 12:19No data—
Sun 18 OctWeert 15:00+2 min+2 min
Sat 17 OctWeert 13:010 min—
Fri 16 OctWeert 12:52No data—
Sun 11 OctWeert 12:530 min—
Sat 10 OctWeert 13:12+6 min+6 min
Fri 9 OctWeert 13:020 min—
Sun 4 OctWeert 12:49No data—
Sat 3 OctWeert 12:49No data—
Fri 2 OctWeert 12:48No data—
Sun 27 SeptWeert 12:49No data—
Sat 26 SeptWeert 12:49No data—
Fri 25 SeptWeert 12:48No data—
Sun 20 SeptWeert 12:48No data—
Sat 19 SeptWeert 12:48No data—
Fri 18 SeptWeert 12:49No data—
Sun 13 SeptWeert 12:49No data—
Sat 12 SeptWeert 12:49No data—
Fri 11 SeptWeert 12:49No data—
Sun 6 SeptWeert 12:50No data—
Sat 5 SeptWeert 12:50No data—
Fri 4 SeptWeert 12:49No data—
Sun 30 AugWeert 12:49No data—
Sat 29 AugWeert 12:49No data—