Train NS 3968 Heerlen – Eindhoven Centraal

Heerlen 17:49 → Eindhoven Centraal 18:51 Daily 1 h 02 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Weert at 18:52 +2 min

  1. Heerlen17:49
  2. Sittard18:04
  3. Roermond18:19
  4. Weert18:34
  5. Eindhoven Centraal18:51

Next service: tomorrow 17:49 from Heerlen · Sat 7 Nov

Next departure 17:49 tomorrow · Heerlen
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 9 full · 5 partial · 12 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 12 full · 5 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Fri 23 Oct Max en route +23 min · last fix heading to Weert +23 min
  • Tue 6 Oct Max en route +6 min · last fix heading to Heerlen +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 6% · 1
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 50% T n=2
  • 100% W n=2
  • 100% T n=3
  • 67% F n=3
  • 100% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 17 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
17:49on time on time
18:04 / 18:05≈ on time ≈ +4 min
18:19 / 18:20≈ on time ≈ +5 min
18:34≈ on time ≈ +5 min
18:51on time +6 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 6 NovWeert 18:52Partial coverage+2 min+2 min
Thu 5 NovSittard 18:59No data—
Wed 4 NovSittard 18:59No data—
Tue 3 NovSittard 18:52No data—
Mon 2 NovSittard 18:520 min—
Sat 31 OctWeert 18:52Partial coverage0 min—
Fri 30 OctWeert 19:04No data—
Thu 29 OctHeerlen 18:530 min—
Wed 28 OctSittard 18:520 min—
Tue 27 OctSittard 19:01No data—
Mon 26 OctSittard 19:010 min—
Sat 24 OctBovenkarspel Flora 21:35No data—
Fri 23 OctWeert 19:38+23 min+23 min
Thu 22 OctWeert 18:530 min—
Wed 21 OctWeert 18:55No data—
Tue 20 OctWeert 18:520 min—
Mon 19 OctWeert 18:53No data—
Sat 17 OctWeert 18:54Partial coverage0 min—
Fri 16 OctWeert 18:52No data—
Thu 15 OctRoermond 18:52No data—
Wed 14 OctWeert 18:53No data—
Tue 13 OctWeert 18:55No data—
Mon 12 OctWeert 18:530 min—
Sat 10 OctWeert 18:52Partial coverage0 min—
Fri 9 OctWeert 18:52Partial coverage0 min—
Thu 8 OctHeerlen 18:530 min—
Wed 7 OctSittard 18:52+1 min+1 min
Tue 6 OctHeerlen 19:05+6 min+6 min
Mon 5 OctSittard 18:520 min—
Sat 3 OctWeert 18:49No data—