Train NS 13932 Heerlen – Eindhoven Centraal

Heerlen 08:49 → Eindhoven Centraal 09:51 Fri, Sat, Sun 1 h 02 min · 5 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Sunday 1 November +1 min

Next service: tomorrow 08:49 from Heerlen · Fri 6 Nov

Next departure 08:49 tomorrow · Heerlen
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 8 full · 1 partial · 1 no data
On-time · 90 days
89%
8/9 runs under 3 min
RT coverage: 8 full · 1 partial · 25 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: +4 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

  • Sat 10 Oct Max en route +6 min · last fix heading to Weert +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 8
  • 3–10 min 11% · 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=3
  • 67% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 9 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
08:49on time on time
09:04 / 09:05≈ on time ≈ +1 min
09:19 / 09:20≈ on time ≈ +2 min
09:34≈ on time ≈ +3 min
09:51on time +4 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 1 NovWeert 10:01Partial coverage+1 min+1 min
Sat 31 OctWeert 10:010 min—
Fri 30 OctWeert 10:010 min—
Sun 25 OctWeert 10:01No data—
Sun 18 OctWeert 10:01+1 min+1 min
Sat 17 OctWeert 09:520 min—
Fri 16 OctWeert 09:530 min—
Sun 11 OctWeert 09:530 min—
Sat 10 OctWeert 10:01+6 min+6 min
Fri 9 OctWeert 10:07+3 min+3 min
Sun 4 OctWeert 09:49No data—
Sat 3 OctWeert 09:50No data—
Fri 2 OctWeert 09:49No data—
Sun 27 SeptWeert 09:49No data—
Sat 26 SeptWeert 09:50No data—
Fri 25 SeptWeert 09:49No data—
Sun 20 SeptWeert 09:49No data—
Sat 19 SeptWeert 09:49No data—
Fri 18 SeptWeert 09:49No data—
Sun 13 SeptWeert 09:49No data—
Sat 12 SeptWeert 09:49No data—
Fri 11 SeptWeert 09:50No data—
Sun 6 SeptWeert 09:50No data—
Sat 5 SeptWeert 09:50No data—
Fri 4 SeptWeert 09:49No data—
Sun 30 AugWeert 09:49No data—
Sat 29 AugWeert 09:49No data—
Fri 28 AugWeert 09:49No data—
Fri 21 AugHeerlen 09:03No data—
Sun 16 AugDen Haag HS 11:58No data—