Train NS 1744 Enschede – Den Haag Centraal

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 12:15 from Enschede · Tue 17 Nov

Next departure 12:15 today · Enschede
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 8 full · 13 partial · 8 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 13 full · 20 partial · 55 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 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

  • Sat 31 Oct Max en route +17 min · last fix heading to Gouda +17 min
  • Sat 24 Oct Max en route +10 min · last fix heading to Gouda +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 31
  • 3–10 min 0% · 0
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=3
  • 100% W n=6
  • 100% T n=3
  • 100% F n=4
  • 67% 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, 33 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
12:15on time on time
12:22 / 12:23≈ on time ≈ on time
12:34 / 12:35≈ on time ≈ on time
13:00 / 13:03≈ on time ≈ on time
13:13 / 13:14≈ on time ≈ on time
13:38 / 13:40≈ on time ≈ +1 min
13:53 / 13:58≈ on time ≈ +1 min
14:16 / 14:17≈ on time ≈ +1 min
14: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
Mon 16 NovGouda 14:35Partial coverage0 min—
Sun 15 NovGouda 14:38Partial coverage+1 min+2 min
Sat 14 NovGouda 14:34Partial coverage0 min—
Fri 13 NovGouda 14:34Partial coverage0 min—
Thu 12 NovGouda 14:38+1 min—
Wed 11 NovGouda 14:34Partial coverage0 min—
Tue 10 NovGouda 14:34Partial coverage0 min—
Mon 9 NovGouda 14:34Partial coverage0 min—
Sun 8 NovLansingerland-Zoetermeer 14:42+1 min+3 min
Sat 7 NovLansingerland-Zoetermeer 14:390 min+1 min
Fri 6 NovGouda 14:34No data—
Thu 5 NovGouda 14:37No data—
Wed 4 NovGouda 14:39Partial coverage+1 min+5 min
Tue 3 NovGouda 14:34No data—
Mon 2 NovGouda 14:29Partial coverage0 min—
Sun 1 NovGouda 14:32Partial coverage0 min—
Sat 31 OctGouda 14:31Partial coverage+17 min+17 min
Fri 30 OctGouda 14:36Partial coverage0 min—
Thu 29 OctGouda 14:45No data—
Wed 28 OctGouda 14:39Partial coverage0 min—
Tue 27 OctGouda 14:31No data—
Mon 26 OctGouda 14:36No data—
Sun 25 OctGouda 14:36No data—
Sat 24 OctGouda 14:52+10 min+10 min
Fri 23 OctGouda 14:45No data—
Thu 22 OctGouda 14:380 min—
Wed 21 OctGouda 14:350 min—
Tue 20 OctGouda 14:400 min—
Mon 19 OctAmersfoort Centraal 13:560 min—
Sun 18 OctAmersfoort Centraal 13:570 min—