Train NS 3929 Eindhoven Centraal – Heerlen

Eindhoven Centraal 10:08 → Heerlen 11:11 Mon, Tue, Wed, Thu, Sat, Sun 1 h 03 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Sittard at 11:24 No data

  1. Eindhoven Centraal10:08
  2. Weert10:26
  3. Roermond10:39
  4. Sittard10:55
  5. Heerlen11:11

Next service: Saturday 10:08 from Eindhoven Centraal · Sat 7 Nov

Next departure 10:08 Saturday · Eindhoven Centraal
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 15 full · 6 partial · 6 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 16 full · 6 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Wed 4 Nov Max en route +4 min · last fix heading to Sittard +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 75% W n=4
  • 100% T n=3
  • 100% F n=1
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 22 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
10:08on time on time
10:26≈ on time ≈ on time
10:39 / 10:40≈ on time ≈ on time
10:55 / 10:56≈ on time ≈ on time
11:11on time on time

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
Thu 5 NovSittard 11:24No data—
Wed 4 NovSittard 11:48+4 min+4 min
Tue 3 NovSittard 11:19No data—
Mon 2 NovSittard 11:130 min—
Sun 1 NovSittard 11:15Partial coverage0 min—
Sat 31 OctSittard 11:12Partial coverage0 min—
Thu 29 OctSittard 11:100 min—
Wed 28 OctSittard 11:160 min—
Tue 27 OctSittard 11:100 min—
Mon 26 OctSittard 11:100 min—
Sun 25 OctSittard 11:13No data—
Sat 24 OctSittard 11:130 min+1 min
Fri 23 OctSittard 11:230 min—
Thu 22 OctSittard 11:240 min—
Wed 21 OctSittard 11:12No data—
Tue 20 OctSittard 11:12No data—
Mon 19 OctSittard 11:240 min—
Sun 18 OctSittard 11:16Partial coverage+2 min+2 min
Sat 17 OctSittard 11:12Partial coverage0 min—
Thu 15 OctSittard 11:13No data—
Wed 14 OctSittard 11:120 min—
Tue 13 OctSittard 11:150 min—
Mon 12 OctSittard 11:120 min—
Sun 11 OctSittard 11:15Partial coverage0 min—
Sat 10 OctSittard 11:13Partial coverage+1 min+2 min
Thu 8 OctSittard 11:120 min—
Wed 7 OctWeert 12:010 min+1 min
Tue 6 OctSittard 11:120 min—
Mon 5 OctSittard 11:17No data—
Sun 4 OctSittard 11:10No data—