Train NS 1732 Enschede – Den Haag Centraal

Enschede 09:15 → Den Haag Centraal 11:35 Daily 2 h 20 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 09:15 from Enschede · Wed 18 Nov

Next departure 09:15 today · Enschede
On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 12 full · 11 partial · 6 no data
On-time · 90 days
89%
31/35 runs under 3 min
RT coverage: 19 full · 16 partial · 53 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Wed 4 Nov Max en route +13 min · last fix heading to Gouda +13 min
  • Mon 16 Nov Max en route +6 min · last fix heading to Gouda +6 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Amersfoort Centraal +5 min
  • Sat 14 Nov Max en route +5 min · last fix heading to Gouda +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 31
  • 3–10 min 9% · 3
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=4
  • 80% W n=5
  • 100% T n=5
  • 100% F n=5
  • 83% S n=6
  • 80% S n=5

Stops and timetable

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

Last 90 days, 35 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
09:15on time on time
09:22 / 09:23≈ on time ≈ on time
09:34 / 09:35≈ on time ≈ on time
10:00 / 10:03≈ on time ≈ +1 min
10:13 / 10:14≈ on time ≈ +1 min
10:38 / 10:40≈ on time ≈ +1 min
10:53 / 10:58≈ on time ≈ +1 min
11:16 / 11:17≈ on time ≈ +1 min
11:35on time +2 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 17 NovGouda 11:37Partial coverage+1 min+2 min
Mon 16 NovGouda 11:52Partial coverage+6 min+6 min
Sun 15 NovGouda 11:34Partial coverage0 min—
Sat 14 NovGouda 11:43+4 min+5 min
Fri 13 NovGouda 11:34Partial coverage+1 min—
Thu 12 NovGouda 11:34Partial coverage0 min—
Wed 11 NovGouda 11:370 min+1 min
Tue 10 NovGouda 11:39Partial coverage0 min+2 min
Mon 9 NovGouda 11:34Partial coverage0 min—
Sun 8 NovLansingerland-Zoetermeer 11:39+1 min+2 min
Sat 7 NovLansingerland-Zoetermeer 11:39+1 min—
Fri 6 NovGouda 11:34No data—
Thu 5 NovGouda 11:34Partial coverage0 min—
Wed 4 NovGouda 11:53Partial coverage+13 min+13 min
Tue 3 NovGouda 11:35No data—
Mon 2 NovGouda 11:380 min—
Sun 1 NovGouda 11:370 min—
Sat 31 OctGouda 11:360 min—
Fri 30 OctGouda 11:360 min—
Thu 29 OctGouda 11:31Partial coverage0 min—
Wed 28 OctGouda 11:44No data—
Tue 27 OctGouda 11:37No data—
Mon 26 OctGouda 11:36No data—
Sun 25 OctGouda 11:37No data—
Sat 24 OctGouda 11:360 min—
Fri 23 OctGouda 11:36Partial coverage0 min—
Thu 22 OctGouda 11:350 min—
Wed 21 OctGouda 11:350 min—
Tue 20 OctGouda 11:370 min—
Mon 19 OctAmersfoort Centraal 10:550 min—