Train NS 1766 Enschede – Den Haag Centraal

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

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 17:45 from Enschede · Thu 19 Nov

Next departure 17:45 today · Enschede
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 3 full · 21 partial · 5 no data
On-time · 90 days
92%
34/37 runs under 3 min
RT coverage: 10 full · 27 partial · 51 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

  • Fri 23 Oct Max en route +8 min · last fix heading to Utrecht Centraal +7 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Gouda +5 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Amersfoort Centraal +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 92% · 34
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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