Train NS 1738 Enschede – Den Haag Centraal

Enschede 10:45 → Den Haag Centraal 13:05 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 10:45 from Enschede · Fri 6 Nov

Next departure 10:45 today · Enschede
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 13 full · 7 partial · 9 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 13 full · 10 partial · 65 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: +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

  • Wed 4 Nov Max en route +19 min · last fix heading to Gouda +19 min
  • Sat 31 Oct Max en route +15 min · last fix heading to Gouda +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 0% · 0
  • 10–30 min 9% · 2
  • 30+ min 0% · 0

On-time by weekday

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