Train NS 1759 Den Haag Centraal – Enschede

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 15:55 from Den Haag Centraal · Sat 7 Nov

Next departure 15:55 today · Den Haag Centraal
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 19 full · 6 partial · 4 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 22 full · 7 partial · 59 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Enschede, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 29
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=4
  • 100% T n=5
  • 100% F n=4
  • 100% 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, 29 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
15:55on time on time
16:13 / 16:14≈ on time ≈ on time
16:32 / 16:37≈ on time ≈ on time
16:50 / 16:52≈ on time ≈ on time
17:16 / 17:17≈ on time ≈ +1 min
17:27 / 17:29≈ on time ≈ +1 min
17:54 / 17:55≈ on time ≈ +1 min
18:06 / 18:07≈ on time ≈ +1 min
18:14on 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
Fri 6 NovHengelo 18:19Partial coverage0 min—
Thu 5 NovHengelo 18:420 min—
Wed 4 NovHengelo 18:19Partial coverage0 min—
Tue 3 NovHengelo 18:190 min—
Mon 2 NovHengelo 18:190 min—
Sun 1 NovHengelo 18:20+1 min—
Sat 31 OctHengelo 18:21+1 min+1 min
Fri 30 OctHengelo 18:24Partial coverage0 min—
Thu 29 OctAlmelo 18:160 min—
Wed 28 OctHengelo 18:21Partial coverage0 min—
Tue 27 OctAlmelo 18:300 min—
Mon 26 OctHengelo 18:21+1 min—
Sun 25 OctDeventer 17:54No data—
Sat 24 OctDeventer 17:570 min—
Fri 23 OctHengelo 18:23Partial coverage0 min—
Thu 22 OctGouda 16:330 min—
Wed 21 OctGouda 16:390 min—
Tue 20 OctGouda 16:440 min—
Mon 19 OctHengelo 18:210 min—
Sun 18 OctUtrecht Centraal 16:510 min—
Sat 17 OctUtrecht Centraal 16:510 min—
Fri 16 OctDen Haag Centraal 17:07No data—
Thu 15 OctUtrecht Centraal 16:510 min—
Wed 14 OctUtrecht Centraal 16:51No data—
Tue 13 OctUtrecht Centraal 16:52No data—
Mon 12 OctUtrecht Centraal 16:520 min—
Sun 11 OctHengelo 18:21+1 min+1 min
Sat 10 OctHengelo 18:22+2 min+2 min
Fri 9 OctHengelo 18:22Partial coverage0 min+1 min
Thu 8 OctAlmelo 18:160 min+1 min