Train NS 1726 Enschede – Den Haag Centraal

Enschede 07:45 → Den Haag Centraal 10:05 Daily 2 h 20 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 07:45 from Enschede · Thu 5 Nov

Next departure 07:45 today · Enschede
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 18 full · 5 partial · 6 no data
On-time · 90 days
89%
39/44 runs under 3 min
RT coverage: 39 full · 5 partial · 43 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: +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

  • Sun 1 Nov Max en route +30 min · last fix heading to Amersfoort Centraal +30 min
  • Thu 20 Aug Max en route +4 min · last fix heading to Utrecht Centraal +4 min
  • Mon 17 Aug Max en route +4 min · last fix heading to Utrecht Centraal +4 min
  • Fri 14 Aug Max en route +3 min · last fix heading to Utrecht Centraal +3 min
  • Sun 11 Oct Max en route +3 min · last fix heading to Amersfoort Centraal +3 min

Distribution · 90 days

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

  • Early 11% · 5
  • On time 77% · 34
  • 3–10 min 9% · 4
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 86% M n=7
  • 100% T n=7
  • 100% W n=7
  • 80% T n=5
  • 83% F n=6
  • 100% S n=8
  • 50% S n=4

Stops and timetable

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

Last 90 days, 44 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
07:45on time on time
07:52 / 07:53≈ on time ≈ on time
08:04 / 08:05≈ on time ≈ on time
08:30 / 08:33≈ on time ≈ +1 min
08:43 / 08:44≈ on time ≈ +1 min
09:08 / 09:10≈ on time ≈ +2 min
09:23 / 09:28≈ on time ≈ +2 min
09:46 / 09:47≈ on time ≈ +3 min
10:05on time +3 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
Wed 4 NovGouda 10:04Partial coverage0 min—
Tue 3 NovGouda 10:070 min—
Mon 2 NovGouda 10:02No data—
Sun 1 NovAmersfoort Centraal 09:44+30 min+30 min
Sat 31 OctGouda 10:010 min—
Fri 30 OctGouda 10:06Partial coverage0 min—
Thu 29 OctGouda 10:060 min—
Wed 28 OctGouda 10:07Partial coverage0 min—
Tue 27 OctGouda 10:070 min—
Mon 26 OctGouda 10:06Partial coverage0 min—
Sun 25 OctGouda 10:06No data—
Sat 24 OctGouda 10:060 min—
Fri 23 OctGouda 10:060 min—
Thu 22 OctGouda 10:08No data—
Wed 21 OctGouda 10:080 min—
Tue 20 OctGouda 10:060 min—
Mon 19 OctAmersfoort Centraal 09:240 min—
Sun 18 OctAmersfoort Centraal 09:29+1 min+1 min
Sat 17 OctAmersfoort Centraal 09:30+2 min+2 min
Fri 16 OctGouda 10:060 min—
Thu 15 OctUtrecht Centraal 10:58No data—
Wed 14 OctGouda 10:19No data—
Tue 13 OctGouda 10:13No data—
Mon 12 OctGouda 10:070 min—
Sun 11 OctAmersfoort Centraal 10:12+3 min+3 min
Sat 10 OctGouda 10:06Partial coverage0 min—
Fri 9 OctGouda 10:09+1 min+1 min
Thu 8 OctGouda 10:070 min—
Wed 7 OctGouda 10:070 min+2 min
Tue 6 OctGouda 10:060 min—