Train NS 3950 Heerlen – Eindhoven Centraal

Heerlen 13:19 → Eindhoven Centraal 14:21 Daily 1 h 02 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Weert at 14:19 +2 min

  1. Heerlen13:19
  2. Sittard13:34
  3. Roermond13:49
  4. Weert14:04
  5. Eindhoven Centraal14:21

Next service: tomorrow 13:19 from Heerlen · Sat 14 Nov

Next departure 13:19 tomorrow · Heerlen
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 20 full · 4 partial · 6 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 26 full · 7 partial · 54 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: +1 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 31
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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
13:19on time on time
13:34 / 13:35≈ on time ≈ on time
13:49 / 13:50≈ on time ≈ +1 min
14:04≈ on time ≈ +1 min
14:21on 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
Fri 13 NovWeert 14:19Partial coverage+2 min+2 min
Thu 12 NovBovenkarspel Flora 17:040 min—
Wed 11 NovBovenkarspel Flora 17:04+1 min—
Tue 10 NovBovenkarspel Flora 17:040 min—
Mon 9 NovBovenkarspel Flora 17:09+9 min+10 min
Sun 8 NovBovenkarspel Flora 17:040 min—
Sat 7 NovBovenkarspel Flora 17:04+2 min+2 min
Fri 6 NovWeert 14:22No data—
Thu 5 NovBovenkarspel Flora 17:03No data—
Wed 4 NovBovenkarspel Flora 17:040 min—
Tue 3 NovBovenkarspel Flora 17:03No data—
Mon 2 NovBovenkarspel Flora 17:04No data—
Sun 1 NovWeert 14:200 min—
Sat 31 OctWeert 14:230 min—
Fri 30 OctWeert 14:23No data—
Thu 29 OctBovenkarspel Flora 17:080 min—
Wed 28 OctBovenkarspel Flora 17:030 min—
Tue 27 OctBovenkarspel Flora 17:030 min—
Mon 26 OctBovenkarspel Flora 17:030 min—
Sun 25 OctWeert 14:27No data—
Sat 24 OctBovenkarspel Flora 17:04+1 min—
Fri 23 OctBovenkarspel Flora 17:040 min—
Thu 22 OctBovenkarspel Flora 17:030 min—
Wed 21 OctBovenkarspel Flora 17:120 min—
Tue 20 OctBovenkarspel Flora 17:070 min—
Mon 19 OctBovenkarspel Flora 17:040 min—
Sun 18 OctWeert 14:25Partial coverage+1 min+3 min
Sat 17 OctWeert 14:22Partial coverage0 min—
Fri 16 OctWeert 14:22Partial coverage0 min—
Thu 15 OctBovenkarspel Flora 17:030 min—