Train NS 1137 Den Haag Centraal – Eindhoven Centraal

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

✓ Today’s run finished

Today, last fix heading to Tilburg at 11:49 0 min

  1. Den Haag Centraal10:19
  2. Den Haag HS10:22
  3. Delft10:30
  4. Rotterdam Centraal10:40
  5. Breda11:07
  6. Tilburg11:23
  7. Eindhoven Centraal11:47

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

Next departure 10:19 tomorrow · Den Haag Centraal
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 11 full · 9 partial · 8 no data
On-time · 90 days
96%
49/51 runs under 3 min
RT coverage: 39 full · 12 partial · 36 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 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

  • Mon 9 Nov Max en route +28 min · last fix heading to Tilburg +10 min
  • Tue 25 Aug Max en route +7 min · last fix heading to Rotterdam Centraal +7 min

Distribution · 90 days

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

  • Early 14% · 7
  • On time 82% · 42
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 88% T n=8
  • 100% W n=5
  • 100% T n=9
  • 100% F n=10
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

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