Train NS 1725 Den Haag Centraal – Enschede

Den Haag Centraal 07:25 → Enschede 09:44 Daily 2 h 19 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Hengelo at 10:14 +15 min

  1. Den Haag Centraal07:25
  2. Gouda07:43
  3. Amersfoort Centraal08:20
  4. Apeldoorn08:46
  5. Deventer08:57
  6. Hengelo09:36
  7. Enschede09:44

Next service: tomorrow 07:25 from Den Haag Centraal · Tue 10 Nov

Next departure 07:25 tomorrow · Den Haag Centraal
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 19 full · 5 partial · 6 no data
On-time · 90 days
94%
62/66 runs under 3 min
RT coverage: 59 full · 7 partial · 21 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: +1 min

Last 30 days

Arrival delay at Enschede, 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 25 Aug Max en route +18 min · last fix heading to Utrecht Centraal +18 min
  • Mon 9 Nov Max en route +15 min · last fix heading to Hengelo +15 min
  • Tue 29 Sept Max en route +8 min · last fix heading to Utrecht Centraal +8 min
  • Wed 23 Sept Max en route +21 min · last fix heading to Hengelo +6 min

Distribution · 90 days

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

  • Early 11% · 7
  • On time 83% · 55
  • 3–10 min 3% · 2
  • 10–30 min 3% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=12
  • 82% T n=11
  • 91% W n=11
  • 100% T n=9
  • 100% F n=11
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

Last 90 days, 66 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
07:25on time on time
07:43 / 07:44≈ on time ≈ on time
08:02 / 08:07≈ on time ≈ +1 min
08:20 / 08:22≈ on time ≈ +1 min
08:46 / 08:47≈ on time ≈ +1 min
08:57 / 08:59≈ on time ≈ +1 min
09:24 / 09:25≈ on time ≈ +2 min
09:36 / 09:37≈ on time ≈ +2 min
09:44on 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
Mon 9 NovHengelo 10:14Partial coverage+15 min+15 min
Sun 8 NovHengelo 09:490 min—
Sat 7 NovHengelo 09:520 min—
Fri 6 NovHengelo 09:52No data—
Thu 5 NovHengelo 10:13Partial coverage0 min—
Wed 4 NovHengelo 09:490 min—
Tue 3 NovHengelo 09:59Partial coverage0 min—
Mon 2 NovHengelo 09:49Partial coverage0 min—
Sun 1 NovHengelo 09:52+1 min+1 min
Sat 31 OctHengelo 09:510 min—
Fri 30 OctHengelo 10:050 min—
Thu 29 OctHengelo 09:51Partial coverage0 min—
Wed 28 OctHengelo 09:51No data—
Tue 27 OctHengelo 10:130 min—
Mon 26 OctHengelo 09:510 min—
Sun 25 OctDeventer 09:34No data—
Sat 24 OctDeventer 09:24+2 min+2 min
Fri 23 OctHengelo 09:510 min—
Thu 22 OctGouda 08:03No data—
Wed 21 OctGouda 08:250 min—
Tue 20 OctGouda 08:040 min—
Mon 19 OctHengelo 09:510 min—
Sun 18 OctUtrecht Centraal 08:24+1 min+2 min
Sat 17 OctUtrecht Centraal 08:20No data—
Fri 16 OctUtrecht Centraal 08:210 min—
Thu 15 OctUtrecht Centraal 08:21No data—
Wed 14 OctUtrecht Centraal 08:210 min—
Tue 13 OctUtrecht Centraal 08:380 min—
Mon 12 OctUtrecht Centraal 08:370 min—
Sun 11 OctHengelo 09:510 min—