Train NS 1730 Enschede – Den Haag Centraal

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

✓ Today’s run finished

Today, last fix heading to Gouda at 11:04 0 min

  1. Enschede08:45
  2. Hengelo08:52
  3. Deventer09:30
  4. Apeldoorn09:43
  5. Amersfoort Centraal10:08
  6. Gouda10:46
  7. Den Haag Centraal11:05

Next service: tomorrow 08:45 from Enschede · Tue 10 Nov

Next departure 08:45 tomorrow · Enschede
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 18 full · 3 partial · 9 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 18 full · 8 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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 8 Nov Max en route +7 min · last fix heading to Amersfoort Centraal +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=3
  • 100% S n=5
  • 75% S n=4

Stops and timetable

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

Last 90 days, 26 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:45on time on time
08:52 / 08:53≈ on time ≈ on time
09:04 / 09:05≈ on time ≈ on time
09:30 / 09:33≈ on time ≈ on time
09:43 / 09:44≈ on time ≈ on time
10:08 / 10:10≈ on time ≈ on time
10:23 / 10:28≈ on time ≈ on time
10:46 / 10:47≈ on time ≈ on time
11:05on time on time

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 9 NovGouda 11:04Partial coverage0 min—
Sun 8 NovAmersfoort Centraal 10:34+7 min+7 min
Sat 7 NovLansingerland-Zoetermeer 11:090 min+1 min
Fri 6 NovGouda 11:22No data—
Thu 5 NovGouda 11:07No data—
Wed 4 NovGouda 11:04Partial coverage0 min—
Tue 3 NovUtrecht Centraal 11:040 min—
Mon 2 NovGouda 11:04Partial coverage0 min—
Sun 1 NovAmersfoort Centraal 10:250 min—
Sat 31 OctGouda 11:06+1 min+1 min
Fri 30 OctGouda 11:07No data—
Thu 29 OctGouda 11:060 min—
Wed 28 OctGouda 11:070 min—
Tue 27 OctGouda 11:070 min—
Mon 26 OctGouda 11:07No data—
Sun 25 OctGouda 11:07No data—
Sat 24 OctGouda 11:060 min—
Fri 23 OctGouda 11:070 min—
Thu 22 OctGouda 11:160 min—
Wed 21 OctGouda 11:140 min—
Tue 20 OctGouda 11:050 min—
Mon 19 OctAmersfoort Centraal 10:330 min—
Sun 18 OctAmersfoort Centraal 10:260 min—
Sat 17 OctGouda 11:010 min—
Fri 16 OctGouda 11:060 min—
Thu 15 OctGouda 11:07No data—
Wed 14 OctGouda 11:06No data—
Tue 13 OctGouda 11:13No data—
Mon 12 OctGouda 11:07No data—
Sun 11 OctAmersfoort Centraal 11:160 min—