Train NS 1768 Enschede – Den Haag Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November No data

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

Next departure 18:15 today · Enschede
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 10 full · 5 partial · 12 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 13 full · 5 partial · 50 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

  • Thu 29 Oct Max en route +14 min · last fix heading to — +14 min
  • Sat 31 Oct Max en route +3 min · last fix heading to Gouda +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 6% · 1
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
18:15on time on time
18:22 / 18:23≈ on time ≈ +1 min
18:34 / 18:35≈ on time ≈ +1 min
19:00 / 19:03≈ on time ≈ +1 min
19:13 / 19:14≈ on time ≈ +1 min
19:38 / 19:40≈ on time ≈ +1 min
19:53 / 19:58≈ on time ≈ +1 min
20:16 / 20:17≈ on time ≈ +1 min
20:35on 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
Thu 5 Nov— 20:35No data—
Wed 4 NovEnschede 20:34Partial coverage0 min—
Sun 1 NovGouda 20:340 min—
Sat 31 OctGouda 20:40Partial coverage+3 min+3 min
Fri 30 OctAlmelo 18:49No data—
Thu 29 Oct— 20:59+14 min+14 min
Wed 28 Oct— 20:390 min—
Tue 27 Oct— 20:37No data—
Mon 26 OctAmersfoort Centraal 21:04No data—
Sun 25 OctGouda 20:37No data—
Sat 24 OctGouda 20:430 min—
Fri 23 OctApeldoorn 20:40Partial coverage+2 min+5 min
Thu 22 OctAlmelo 20:07No data—
Wed 21 OctAlmelo 20:38No data—
Tue 20 OctAlmelo 19:39No data—
Mon 19 OctAlmelo 19:550 min—
Sun 18 OctAmersfoort Centraal 19:59+2 min+2 min
Sat 17 OctGouda 20:360 min—
Fri 16 Oct— 20:36No data—
Thu 15 Oct— 20:36No data—
Wed 14 OctAmersfoort Centraal 20:36No data—
Tue 13 Oct— 20:39No data—
Mon 12 Oct— 20:360 min—
Sun 11 OctGouda 20:370 min—
Sat 10 OctGouda 20:37Partial coverage0 min—
Fri 9 OctAlmelo 20:38Partial coverage+2 min+2 min
Thu 8 Oct— 03:250 min—
Wed 7 Oct— 23:040 min+2 min
Tue 6 Oct— 20:360 min—
Mon 5 Oct— 20:370 min—