Train NS 1750 Enschede – Den Haag Centraal

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

✓ Today’s run finished

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

  1. Enschede13:45
  2. Hengelo13:52
  3. Deventer14:30
  4. Apeldoorn14:43
  5. Amersfoort Centraal15:08
  6. Gouda15:46
  7. Den Haag Centraal16:05

Next service: tomorrow 13:45 from Enschede · Sat 21 Nov

Next departure 13:45 tomorrow · Enschede
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 13 full · 13 partial · 4 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 20 full · 19 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 19 Nov Max en route +4 min · last fix heading to Gouda +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 38
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=5
  • 100% W n=6
  • 80% T n=5
  • 100% F n=5
  • 100% 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, 39 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
13:45on time on time
13:52 / 13:53≈ on time ≈ on time
14:04 / 14:05≈ on time ≈ on time
14:30 / 14:33≈ on time ≈ +1 min
14:43 / 14:44≈ on time ≈ +1 min
15:08 / 15:10≈ on time ≈ +1 min
15:23 / 15:28≈ on time ≈ +1 min
15:46 / 15:47≈ on time ≈ +2 min
16:05on 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
Fri 20 NovGouda 16:04Partial coverage+1 min+1 min
Thu 19 NovGouda 16:09Partial coverage+4 min+4 min
Wed 18 NovGouda 16:07Partial coverage+1 min+3 min
Tue 17 NovGouda 16:04Partial coverage0 min+1 min
Mon 16 NovGouda 16:08Partial coverage0 min—
Sun 15 NovGouda 16:02+1 min+1 min
Sat 14 NovGouda 16:04Partial coverage0 min—
Fri 13 NovGouda 16:07Partial coverage+1 min+2 min
Thu 12 NovGouda 16:09+3 min+6 min
Wed 11 NovGouda 16:04Partial coverage0 min—
Tue 10 NovGouda 16:02Partial coverage+1 min+1 min
Mon 9 NovGouda 16:09Partial coverage+1 min+4 min
Sun 8 NovLansingerland-Zoetermeer 16:12+2 min+2 min
Sat 7 NovLansingerland-Zoetermeer 16:12+2 min+3 min
Fri 6 NovGouda 16:04No data—
Thu 5 NovGouda 16:19Partial coverage0 min—
Wed 4 NovGouda 16:07Partial coverage+1 min+3 min
Tue 3 NovGouda 16:04No data—
Mon 2 NovGouda 16:07Partial coverage0 min—
Sun 1 NovGouda 16:010 min—
Sat 31 OctGouda 16:060 min—
Fri 30 OctGouda 16:060 min—
Thu 29 OctGouda 16:060 min—
Wed 28 OctGouda 16:060 min—
Tue 27 OctGouda 16:090 min—
Mon 26 OctGouda 16:090 min—
Sun 25 OctGouda 16:06No data—
Sat 24 OctGouda 16:09+2 min+2 min
Fri 23 OctGouda 16:090 min—
Thu 22 OctGouda 16:07No data—