Train NS 1141 Den Haag Centraal – Eindhoven Centraal

Den Haag Centraal 11:19 → Eindhoven Centraal 12:47 Daily 1 h 28 min · 7 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Tilburg at 12:48 0 min

  1. Den Haag Centraal11:19
  2. Den Haag HS11:22
  3. Delft11:30
  4. Rotterdam Centraal11:40
  5. Breda12:07
  6. Tilburg12:23
  7. Eindhoven Centraal12:47

Next service: tomorrow 11:19 from Den Haag Centraal · Tue 10 Nov

Next departure 11:19 tomorrow · Den Haag Centraal
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 11 full · 9 partial · 8 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 13 full · 13 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 26
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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
11:19on time on time
11:22 / 11:23≈ on time ≈ on time
11:30≈ on time ≈ on time
11:40 / 11:45≈ on time ≈ on time
12:07 / 12:08≈ on time ≈ on time
12:23 / 12:25≈ on time ≈ on time
12:47on 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
Mon 9 NovTilburg 12:48Partial coverage0 min—
Fri 6 NovTilburg 12:49No data—
Thu 5 NovTilburg 12:39Partial coverage0 min—
Wed 4 NovTilburg 12:48Partial coverage0 min—
Tue 3 NovTilburg 12:48No data—
Mon 2 NovTilburg 12:49No data—
Sun 1 NovBreda 12:250 min—
Sat 31 OctBreda 12:240 min—
Fri 30 OctTilburg 12:390 min—
Thu 29 OctTilburg 12:49Partial coverage0 min—
Wed 28 OctTilburg 12:49No data—
Tue 27 OctTilburg 12:49No data—
Mon 26 OctTilburg 12:48Partial coverage0 min—
Sun 25 OctTilburg 13:01No data—
Sat 24 OctTilburg 12:480 min+1 min
Fri 23 OctTilburg 12:480 min—
Thu 22 OctTilburg 12:590 min—
Wed 21 OctTilburg 12:49No data—
Tue 20 OctTilburg 12:510 min—
Mon 19 OctTilburg 13:10Partial coverage0 min—
Sun 18 OctTilburg 12:480 min+4 min
Sat 17 OctTilburg 12:480 min—
Fri 16 OctTilburg 12:580 min—
Thu 15 OctTilburg 12:49Partial coverage0 min—
Wed 14 OctTilburg 13:00Partial coverage0 min—
Tue 13 OctRotterdam Centraal 13:08No data—
Mon 12 OctTilburg 12:49Partial coverage0 min—
Sun 11 OctTilburg 12:480 min—
Sat 10 OctTilburg 12:480 min—
Fri 9 OctTilburg 12:53+1 min+5 min