Train NS 1722 Enschede – Den Haag Centraal

Enschede 06:45 → Den Haag Centraal 09:08 Daily 2 h 23 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Gouda at 09:13 No data

  1. Enschede06:45
  2. Hengelo06:52
  3. Deventer07:30
  4. Apeldoorn07:43
  5. Amersfoort Centraal08:08
  6. Gouda08:46
  7. Den Haag Centraal09:08

Next service: tomorrow 06:45 from Enschede · Fri 6 Nov

Next departure 06:45 tomorrow · Enschede
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 19 full · 8 partial · 3 no data
On-time · 90 days
93%
52/56 runs under 3 min
RT coverage: 47 full · 9 partial · 31 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

  • Fri 9 Oct Max en route +17 min · last fix heading to Gouda +15 min
  • Thu 17 Sept Max en route +6 min · last fix heading to Utrecht Centraal +5 min
  • Wed 16 Sept Max en route +6 min · last fix heading to Amersfoort Centraal +5 min
  • Tue 8 Sept Max en route +7 min · last fix heading to Amersfoort Centraal +5 min

Distribution · 90 days

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

  • Early 38% · 21
  • On time 55% · 31
  • 3–10 min 5% · 3
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 90% T n=10
  • 90% W n=10
  • 86% T n=7
  • 91% F n=11
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

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