Train NS 3974 Heerlen → Eindhoven Centraal

Heerlen 19:19 → Eindhoven Centraal 20:21 Sun 1 h 02 min · 5 stops NS (Nederlandse Spoorwegen)

NS 3974 Heerlen–Eindhoven Centraal: final delay under 3 min on 5 of its 6 runs with data in the last 30 days (83%). Median final delay: 0 min. Running now, on time. Expected at Eindhoven Centraal: 20:21. TrainsRadar data as of 22 Nov 2026, 19:43 (GMT+1).

Running now · updated 19:42

Heading to Eindhoven Centraal 0 min

Estimated arrival at Eindhoven Centraal 20:21 · 91 km/h

  1. Heerlen19:19
  2. Sittard19:34
  3. Roermond19:49
  4. Weert20:04
  5. Eindhoven Centraal20:21

Today it is running no worse than usual: typical arrival delay is 0 min; 83% of the last 6 runs arrived on time.

On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 5 full · 1 partial · 3 no data
On-time · 90 days
88%
7/8 runs under 3 min
RT coverage: 5 full · 3 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +9 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

  • Sun 1 Nov Max en route +18 min · last fix heading to Weert +18 min

Distribution · 90 days

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=2
  • 83% S n=6

Stops and timetable

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

Last 90 days, 8 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 10Today
19:19on time +2 min
19:34 / 19:35≈ on time ≈ +6 min
19:49 / 19:50≈ on time ≈ +7 min
20:04≈ on time ≈ +9 min
20:21on time +11 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 22 NovSittard 19:39Partial coverage0 min—
Sun 15 NovHeerlen 19:340 min+1 min
Sat 14 NovHeerlen 19:340 min+1 min
Sun 8 NovBovenkarspel Flora 23:140 min—
Sat 7 NovBovenkarspel Flora 23:030 min—
Tue 3 Nov— 19:48No data—
Sun 1 NovWeert 20:37+18 min+18 min
Sun 25 OctWeert 20:31No data—
Sat 24 OctAmsterdam Amstel 23:07No data—
Sun 18 OctWeert 20:22Partial coverage0 min—
Sun 11 OctWeert 20:23Partial coverage0 min—
Sun 4 OctWeert 20:23No data—
Sun 27 SeptWeert 20:22No data—
Sun 20 SeptWeert 20:19No data—
Sun 13 SeptWeert 20:19No data—
Sun 6 SeptWeert 20:19No data—
Sat 5 SeptHeerlen 19:33No data—
Sun 30 AugWeert 20:19No data—