Train NS 1734 Enschede – Den Haag Centraal

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

✓ Today’s run finished

Today, last fix heading to Gouda at 12:09 +2 min

  1. Enschede09:45
  2. Hengelo09:52
  3. Deventer10:30
  4. Apeldoorn10:43
  5. Amersfoort Centraal11:08
  6. Gouda11:46
  7. Den Haag Centraal12:05

Next service: tomorrow 09:45 from Enschede · Sun 15 Nov

Next departure 09:45 tomorrow · Enschede
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 21 full · 4 partial · 5 no data
On-time · 90 days
97%
32/33 runs under 3 min
RT coverage: 27 full · 6 partial · 56 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

  • Tue 10 Nov Max en route +6 min · last fix heading to Gouda +4 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 97% · 32
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=5
  • 100% S n=6
  • 100% S n=4

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