Train NS 1714 Enschede – Den Haag Centraal

Enschede 04:46 → Den Haag Centraal 07:05 Mon, Tue, Wed, Thu, Fri 2 h 19 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Gouda at 07:08 +1 min

  1. Enschede04:46
  2. Hengelo04:53
  3. Deventer05:30
  4. Apeldoorn05:43
  5. Amersfoort Centraal06:08
  6. Gouda06:46
  7. Den Haag Centraal07:05

Next service: tomorrow 04:46 from Enschede · Fri 20 Nov

Next departure 04:46 tomorrow · Enschede
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 16 full · 5 partial · 1 no data
On-time · 90 days
93%
56/60 runs under 3 min
RT coverage: 54 full · 6 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 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

  • Wed 14 Oct Max en route +15 min · last fix heading to Gouda +15 min
  • Tue 25 Aug Max en route +33 min · last fix heading to Utrecht Centraal +5 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Gouda +4 min
  • Tue 13 Oct Max en route +4 min · last fix heading to Gouda +3 min

Distribution · 90 days

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

  • Early 10% · 6
  • On time 83% · 50
  • 3–10 min 5% · 3
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 83% T n=12
  • 92% W n=12
  • 92% T n=13
  • 100% F n=11
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 60 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
04:46on time on time
04:53 / 04:54≈ on time ≈ on time
05:04 / 05:05≈ on time ≈ on time
05:30 / 05:33≈ on time ≈ +1 min
05:43 / 05:44≈ on time ≈ +1 min
06:08 / 06:10≈ on time ≈ +1 min
06:23 / 06:28≈ on time ≈ +1 min
06:46 / 06:47≈ on time ≈ +1 min
07:05on 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 19 NovGouda 07:08Partial coverage+1 min+1 min
Wed 18 NovGouda 07:09+1 min+3 min
Tue 17 NovUtrecht Centraal 07:23Partial coverage0 min+8 min
Mon 16 NovGouda 07:040 min—
Fri 13 NovGouda 07:02+2 min+2 min
Thu 12 NovGouda 07:12Partial coverage+4 min+4 min
Wed 11 NovGouda 07:070 min—
Tue 10 NovGouda 07:04+2 min+2 min
Mon 9 NovGouda 07:09+1 min+3 min
Fri 6 NovGouda 07:04No data—
Thu 5 NovGouda 07:230 min—
Wed 4 NovGouda 07:07+1 min+1 min
Tue 3 NovGouda 07:040 min+2 min
Mon 2 NovApeldoorn 07:230 min—
Fri 30 OctGouda 07:07+1 min+1 min
Thu 29 OctGouda 07:07Partial coverage+1 min—
Wed 28 OctGouda 07:07+1 min+2 min
Tue 27 OctGouda 07:07Partial coverage0 min—
Mon 26 OctGouda 07:11+2 min+4 min
Fri 23 OctGouda 07:070 min—
Thu 22 OctUtrecht Centraal 07:120 min—
Wed 21 OctGouda 07:10+2 min+2 min
Tue 20 OctGouda 07:060 min+1 min
Mon 19 OctAmersfoort Centraal 06:250 min+2 min
Fri 16 OctGouda 07:060 min—
Thu 15 OctGouda 07:060 min—
Wed 14 OctGouda 07:22+15 min+15 min
Tue 13 OctGouda 07:13+3 min+4 min
Mon 12 OctGouda 07:070 min+1 min
Fri 9 OctGouda 07:07+1 min+4 min