Train NS 1736 Enschede – Den Haag Centraal

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

✓ Today’s run finished

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

  1. Enschede10:15
  2. Hengelo10:22
  3. Deventer11:00
  4. Apeldoorn11:13
  5. Amersfoort Centraal11:38
  6. Gouda12:16
  7. Den Haag Centraal12:35

Next service: tomorrow 10:15 from Enschede · Sat 21 Nov

Next departure 10:15 tomorrow · Enschede
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 10 full · 15 partial · 5 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 21 full · 19 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Fri 9 Oct Max en route +15 min · last fix heading to Gouda +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 39
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=4
  • 100% W n=7
  • 100% T n=6
  • 80% F n=5
  • 100% 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, 40 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
10:15on time on time
10:22 / 10:23≈ on time ≈ on time
10:34 / 10:35≈ on time ≈ on time
11:00 / 11:03≈ on time ≈ on time
11:13 / 11:14≈ on time ≈ on time
11:38 / 11:40≈ on time ≈ on time
11:53 / 11:58≈ on time ≈ +1 min
12:16 / 12:17≈ on time ≈ +1 min
12: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
Fri 20 NovGouda 12:39Partial coverage+2 min+4 min
Thu 19 NovGouda 12:49+1 min+1 min
Wed 18 NovGouda 12:34Partial coverage0 min—
Tue 17 NovGouda 12:37Partial coverage+1 min+1 min
Mon 16 NovGouda 12:39Partial coverage+2 min+3 min
Sun 15 NovGouda 12:38+1 min—
Sat 14 NovGouda 12:37Partial coverage+1 min+2 min
Fri 13 NovGouda 12:37Partial coverage+1 min+1 min
Thu 12 NovGouda 12:340 min—
Wed 11 NovGouda 12:37Partial coverage0 min—
Tue 10 NovGouda 12:39Partial coverage+2 min+5 min
Mon 9 NovGouda 12:34Partial coverage0 min—
Sun 8 NovLansingerland-Zoetermeer 12:390 min+1 min
Sat 7 NovLansingerland-Zoetermeer 12:390 min—
Fri 6 NovGouda 12:34No data—
Thu 5 NovGouda 12:43Partial coverage0 min—
Wed 4 NovGouda 12:34Partial coverage0 min—
Tue 3 NovAlmelo 12:49No data—
Mon 2 NovGouda 12:29Partial coverage0 min—
Sun 1 NovGouda 12:32+2 min+2 min
Sat 31 OctGouda 12:41Partial coverage+1 min+3 min
Fri 30 OctGouda 12:36Partial coverage0 min—
Thu 29 OctGouda 12:310 min—
Wed 28 OctGouda 12:45Partial coverage0 min—
Tue 27 OctGouda 12:37No data—
Mon 26 OctGouda 12:360 min—
Sun 25 OctGouda 12:36No data—
Sat 24 OctGouda 12:360 min—
Fri 23 OctGouda 12:38No data—
Thu 22 OctGouda 12:380 min—