Train NS 13937 Eindhoven Centraal – Heerlen

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

✓ Today’s run finished

Today, last fix heading to Sittard at 13:14 +2 min

  1. Eindhoven Centraal12:08
  2. Weert12:26
  3. Roermond12:39
  4. Sittard12:55
  5. Heerlen13:11

Next service: Friday 12:08 from Eindhoven Centraal · Fri 13 Nov

Next departure 12:08 Friday · Eindhoven Centraal
On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 2 full · 4 partial · 6 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 3 full · 4 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sat 10 Oct Max en route +5 min · last fix heading to Sittard +5 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 86% · 6
  • 3–10 min 14% · 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
  • 50% S n=2
  • 100% S n=3

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
12:08on time on time
12:26— —
12:39 / 12:40— —
12:55 / 12:56— —
13: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 NovSittard 13:14Partial coverage+2 min+2 min
Sat 7 NovSittard 13:12Partial coverage0 min—
Fri 6 NovSittard 13:09No data—
Sun 1 NovSittard 13:130 min+1 min
Sat 31 OctSittard 13:10No data—
Fri 30 OctSittard 13:10No data—
Sun 25 OctSittard 13:19No data—
Sun 18 OctSittard 13:20No data—
Sat 17 OctSittard 13:10No data—
Fri 16 OctSittard 13:12Partial coverage0 min—
Sun 11 OctSittard 13:12Partial coverage0 min—
Sat 10 OctSittard 13:14+5 min+5 min
Fri 9 OctSittard 13:10+1 min+1 min
Sun 4 OctSittard 13:11No data—
Sat 3 OctSittard 13:13No data—
Fri 2 OctSittard 13:10No data—
Sun 27 SeptSittard 13:10No data—
Sat 26 SeptSittard 13:11No data—
Fri 25 SeptSittard 13:10No data—
Sun 20 SeptSittard 13:10No data—
Sat 19 SeptSittard 13:11No data—
Fri 18 SeptSittard 13:14No data—
Sun 13 SeptSittard 13:21No data—
Sat 12 SeptSittard 13:30No data—
Fri 11 SeptSittard 13:10No data—
Sun 6 SeptWeert 12:40No data—
Sat 5 SeptWeert 12:40No data—
Fri 4 SeptSittard 13:18No data—
Sun 30 AugSittard 13:10No data—
Sat 29 AugSittard 13:13No data—