Train NS 1155 Den Haag Centraal – Eindhoven Centraal

Den Haag Centraal 14:49 → Eindhoven Centraal 16:17 Daily 1 h 28 min · 7 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Tilburg at 16:19 0 min

  1. Den Haag Centraal14:49
  2. Den Haag HS14:52
  3. Delft15:00
  4. Rotterdam Centraal15:10
  5. Breda15:37
  6. Tilburg15:53
  7. Eindhoven Centraal16:17

Next service: tomorrow 14:49 from Den Haag Centraal · Fri 13 Nov

Next departure 14:49 tomorrow · Den Haag Centraal
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 11 full · 9 partial · 8 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 14 full · 14 partial · 55 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: +1 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

  • Wed 4 Nov Max en route +22 min · last fix heading to Tilburg +21 min
  • Sat 31 Oct Max en route +5 min · last fix heading to Breda +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 75% W n=4
  • 100% T n=5
  • 100% F n=4
  • 75% 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, 28 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
14:49on time on time
14:52 / 14:53≈ on time ≈ on time
15:00≈ on time ≈ on time
15:10 / 15:15≈ on time ≈ on time
15:37 / 15:38≈ on time ≈ on time
15:53 / 15:55≈ on time ≈ on time
16:17on 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 12 NovTilburg 16:19Partial coverage0 min+1 min
Wed 11 NovTilburg 16:18Partial coverage0 min+3 min
Tue 10 NovTilburg 16:19Partial coverage0 min—
Mon 9 NovTilburg 16:19Partial coverage0 min+1 min
Fri 6 NovTilburg 16:54No data—
Thu 5 NovTilburg 16:20No data—
Wed 4 NovTilburg 16:39Partial coverage+21 min+22 min
Tue 3 NovTilburg 17:05Partial coverage0 min—
Mon 2 NovTilburg 16:19No data—
Sun 1 NovBreda 15:550 min—
Sat 31 OctBreda 15:57+5 min+5 min
Fri 30 OctTilburg 16:190 min—
Thu 29 OctTilburg 16:19Partial coverage0 min—
Wed 28 OctTilburg 16:18No data—
Tue 27 OctTilburg 16:19No data—
Mon 26 OctTilburg 16:180 min—
Sun 25 OctTilburg 16:25No data—
Sat 24 OctTilburg 16:200 min+1 min
Fri 23 OctTilburg 16:300 min—
Thu 22 OctTilburg 16:390 min—
Wed 21 OctTilburg 16:210 min—
Tue 20 OctTilburg 16:09No data—
Mon 19 OctTilburg 16:24Partial coverage0 min—
Sun 18 OctTilburg 16:180 min—
Sat 17 OctTilburg 16:190 min—
Fri 16 OctTilburg 16:180 min—
Thu 15 OctTilburg 16:19Partial coverage0 min—
Wed 14 OctTilburg 16:19No data—
Tue 13 OctTilburg 16:21No data—
Mon 12 OctTilburg 16:19Partial coverage0 min+2 min