Train NS 1758 Enschede – Den Haag Centraal

Enschede 15:45 → Den Haag Centraal 18:05 Daily 2 h 20 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 15:45 from Enschede · Fri 6 Nov

Next departure 15:45 today · Enschede
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 16 full · 4 partial · 8 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 18 full · 5 partial · 64 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 Den Haag 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 5 Oct Max en route +15 min · last fix heading to Gouda +15 min
  • Sun 18 Oct Max en route +9 min · last fix heading to Amersfoort Centraal +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
15:45on time on time
15:52 / 15:53≈ on time ≈ on time
16:04 / 16:05≈ on time ≈ +1 min
16:30 / 16:33≈ on time ≈ +1 min
16:43 / 16:44≈ on time ≈ +1 min
17:08 / 17:10≈ on time ≈ +2 min
17:23 / 17:28≈ on time ≈ +2 min
17:46 / 17:47≈ on time ≈ +3 min
18:05on time +3 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
Thu 5 NovGouda 18:04Partial coverage0 min—
Wed 4 NovGouda 18:090 min—
Tue 3 NovGouda 18:07Partial coverage0 min—
Mon 2 NovGouda 17:59No data—
Sun 1 NovGouda 18:070 min—
Sat 31 OctGouda 18:060 min—
Fri 30 OctGouda 18:010 min—
Thu 29 OctGouda 18:180 min—
Wed 28 OctGouda 18:110 min—
Tue 27 OctGouda 18:070 min—
Mon 26 OctGouda 18:220 min—
Sun 25 OctGouda 18:06No data—
Sat 24 OctGouda 18:060 min—
Fri 23 OctGouda 18:06No data—
Thu 22 OctGouda 18:07No data—
Wed 21 OctGouda 18:05No data—
Tue 20 OctGouda 18:080 min—
Mon 19 OctAmersfoort Centraal 17:280 min—
Sun 18 OctAmersfoort Centraal 17:44+9 min+9 min
Sat 17 OctGouda 18:110 min—
Thu 15 OctGouda 18:06No data—
Wed 14 OctGouda 18:07No data—
Tue 13 OctGouda 18:07No data—
Mon 12 OctGouda 18:070 min—
Sun 11 OctGouda 18:01Partial coverage0 min—
Sat 10 OctGouda 18:06Partial coverage0 min—
Fri 9 OctGouda 18:09+1 min+2 min
Thu 8 OctGouda 18:10+1 min—
Wed 7 OctGouda 18:060 min—
Tue 6 OctGouda 18:09Partial coverage+2 min+3 min