Train NS 1720 Enschede – Den Haag Centraal

Enschede 06:15 → Den Haag Centraal 08:35 Mon, Tue, Wed, Thu, Fri, Sat 2 h 20 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Gouda at 08:34 No data

  1. Enschede06:15
  2. Hengelo06:22
  3. Deventer07:00
  4. Apeldoorn07:13
  5. Amersfoort Centraal07:38
  6. Gouda08:16
  7. Den Haag Centraal08:35

Next service: tomorrow 06:15 from Enschede · Sat 7 Nov

Next departure 06:15 tomorrow · Enschede
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 14 full · 6 partial · 7 no data
On-time · 90 days
87%
47/54 runs under 3 min
RT coverage: 46 full · 8 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Tue 15 Sept Max en route +11 min · last fix heading to Amersfoort Centraal +11 min
  • Mon 21 Sept Max en route +13 min · last fix heading to Amersfoort Centraal +9 min
  • Thu 24 Sept Max en route +10 min · last fix heading to Amersfoort Centraal +9 min
  • Thu 17 Sept Max en route +9 min · last fix heading to Amersfoort Centraal +8 min
  • Fri 11 Sept Max en route +6 min · last fix heading to Utrecht Centraal +5 min

Distribution · 90 days

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

  • Early 33% · 18
  • On time 54% · 29
  • 3–10 min 11% · 6
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 90% M n=10
  • 73% T n=11
  • 100% W n=10
  • 80% T n=10
  • 90% F n=10
  • 100% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 54 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:15on time on time
06:22 / 06:23≈ on time ≈ on time
06:34 / 06:35≈ on time ≈ +1 min
07:00 / 07:03≈ on time ≈ +2 min
07:13 / 07:14≈ on time ≈ +3 min
07:38 / 07:40≈ on time ≈ +3 min
07:53 / 07:58≈ on time ≈ +3 min
08:16 / 08:17≈ on time ≈ +4 min
08:35on time +5 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 6 NovGouda 08:34No data—
Thu 5 NovGouda 08:38No data—
Wed 4 NovGouda 08:37Partial coverage0 min—
Tue 3 NovGouda 09:320 min—
Mon 2 NovGouda 08:340 min—
Sat 31 OctAmersfoort Centraal 08:410 min—
Fri 30 OctGouda 08:310 min—
Thu 29 OctGouda 08:45Partial coverage0 min+5 min
Wed 28 OctGouda 08:37Partial coverage0 min—
Tue 27 OctGouda 08:41Partial coverage0 min—
Mon 26 OctGouda 08:36Partial coverage0 min—
Sun 25 OctGouda 08:36No data—
Sat 24 OctGouda 08:36+2 min+2 min
Fri 23 OctGouda 08:470 min—
Thu 22 OctGouda 08:400 min—
Wed 21 OctGouda 08:350 min—
Tue 20 OctGouda 08:410 min—
Mon 19 OctAlmelo 07:540 min—
Sat 17 OctAmersfoort Centraal 07:56No data—
Fri 16 OctGouda 08:370 min—
Thu 15 OctGouda 08:43No data—
Wed 14 OctGouda 08:37No data—
Tue 13 OctAmersfoort Centraal 08:380 min—
Mon 12 OctGouda 08:39No data—
Sat 10 OctAmersfoort Centraal 08:430 min+3 min
Fri 9 OctGouda 08:360 min—
Thu 8 OctGouda 08:41Partial coverage+1 min+3 min
Wed 7 OctGouda 08:36Partial coverage0 min—
Tue 6 OctGouda 08:42Partial coverage+2 min+3 min
Mon 5 OctGouda 08:35−3 min—