Train NS 1728 Enschede – Den Haag Centraal

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

It has not run yet today

Last recorded run: Thursday 19 November +2 min

Next service: today 08:15 from Enschede · Fri 20 Nov

Next departure 08:15 today · Enschede
On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 11 full · 14 partial · 4 no data
On-time · 90 days
84%
54/64 runs under 3 min
RT coverage: 47 full · 17 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
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

  • Thu 1 Oct Max en route +20 min · last fix heading to Amersfoort Centraal +20 min
  • Mon 16 Nov Max en route +15 min · last fix heading to Gouda +15 min
  • Fri 18 Sept Max en route +12 min · last fix heading to Amersfoort Centraal +12 min
  • Sat 24 Oct Max en route +8 min · last fix heading to Gouda +8 min
  • Fri 2 Oct Max en route +18 min · last fix heading to Amersfoort Centraal +8 min

Distribution · 90 days

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

  • Early 13% · 8
  • On time 72% · 46
  • 3–10 min 11% · 7
  • 10–30 min 5% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 82% M n=11
  • 90% T n=10
  • 100% W n=10
  • 73% T n=11
  • 73% F n=11
  • 83% 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, 64 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
08:15on time on time
08:22 / 08:23≈ on time ≈ on time
08:34 / 08:35≈ on time ≈ +1 min
09:00 / 09:03≈ on time ≈ +2 min
09:13 / 09:14≈ on time ≈ +3 min
09:38 / 09:40≈ on time ≈ +4 min
09:53 / 09:58≈ on time ≈ +5 min
10:16 / 10:17≈ on time ≈ +6 min
10:35on time +7 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 19 NovGouda 10:43Partial coverage+2 min+3 min
Wed 18 NovGouda 10:34Partial coverage0 min—
Tue 17 NovGouda 10:34Partial coverage0 min—
Mon 16 NovGouda 11:04Partial coverage+15 min+15 min
Sun 15 NovAmersfoort Centraal 10:42+1 min+2 min
Sat 14 NovGouda 10:340 min—
Fri 13 NovGouda 10:340 min—
Thu 12 NovGouda 10:34Partial coverage0 min—
Wed 11 NovGouda 10:37Partial coverage0 min—
Tue 10 NovGouda 10:37Partial coverage0 min—
Mon 9 NovGouda 10:34Partial coverage+2 min+2 min
Sun 8 NovAmersfoort Centraal 09:540 min—
Sat 7 NovLansingerland-Zoetermeer 10:39+1 min+2 min
Fri 6 NovGouda 10:39No data—
Thu 5 NovGouda 10:34Partial coverage0 min—
Wed 4 NovGouda 10:34Partial coverage0 min—
Tue 3 NovGouda 10:59No data—
Mon 2 NovGouda 10:34Partial coverage0 min—
Sun 1 NovAmersfoort Centraal 09:540 min—
Sat 31 OctGouda 10:310 min—
Fri 30 OctGouda 10:31Partial coverage0 min—
Thu 29 OctGouda 10:41No data—
Wed 28 OctGouda 10:36Partial coverage0 min—
Tue 27 OctGouda 10:370 min—
Mon 26 OctGouda 10:36Partial coverage0 min—
Sun 25 OctGouda 10:36No data—
Sat 24 OctGouda 10:52+8 min+8 min
Fri 23 OctGouda 10:470 min—
Thu 22 OctGouda 10:350 min—
Wed 21 OctGouda 10:430 min—