Train NS 1752 Enschede – Den Haag Centraal

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

✓ Today’s run finished

Today, last fix heading to Gouda at 16:32 +1 min

  1. Enschede14:15
  2. Hengelo14:22
  3. Deventer15:00
  4. Apeldoorn15:13
  5. Amersfoort Centraal15:38
  6. Gouda16:16
  7. Den Haag Centraal16:35

Next service: tomorrow 14:15 from Enschede · Fri 20 Nov

Next departure 14:15 tomorrow · Enschede
On-time · 30 days
84%
21/25 runs under 3 min
RT coverage: 14 full · 11 partial · 5 no data
On-time · 90 days
89%
33/37 runs under 3 min
RT coverage: 21 full · 16 partial · 52 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: +10 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

  • Sat 31 Oct Max en route +26 min · last fix heading to Amersfoort Centraal +26 min
  • Mon 16 Nov Max en route +18 min · last fix heading to Gouda +18 min
  • Wed 18 Nov Max en route +15 min · last fix heading to Gouda +15 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Gouda +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 33
  • 3–10 min 3% · 1
  • 10–30 min 8% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=5
  • 86% W n=7
  • 80% T n=5
  • 100% F n=3
  • 83% S n=6
  • 100% S n=5

Stops and timetable

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

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