Train NS 1740 Enschede – Den Haag Centraal

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

✓ Today’s run finished

Today, last fix heading to Gouda at 14:04 No data

  1. Enschede11:15
  2. Hengelo11:22
  3. Deventer12:00
  4. Apeldoorn12:13
  5. Amersfoort Centraal12:38
  6. Gouda13:16
  7. Den Haag Centraal13:35

Next service: tomorrow 11:15 from Enschede · Fri 6 Nov

Next departure 11:15 tomorrow · Enschede
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 14 full · 4 partial · 12 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 14 full · 6 partial · 69 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 +9 min · last fix heading to Gouda +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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