Train NS 1775 Den Haag Centraal – Enschede

Den Haag Centraal 19:55 → Enschede 22:14 Daily 2 h 19 min · 9 stops NS (Nederlandse Spoorwegen)

Running now · updated 22:31

Heading to Enschede 0 min

Estimated arrival at Enschede 22:14 · 0 km/h

  1. Den Haag Centraal19:55
  2. Gouda20:13
  3. Amersfoort Centraal20:50
  4. Apeldoorn21:16
  5. Deventer21:27
  6. Hengelo22:06
  7. Enschede22:14

Today it is running no worse than usual: typical arrival delay is 0 min; 90% of the last 20 runs arrived on time.

On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 18 full · 2 partial · 9 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 20 full · 2 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 9 Oct Max en route +10 min · last fix heading to — +10 min
  • Mon 2 Nov Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=2
  • 100% W n=4
  • 100% T n=4
  • 50% F n=2
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 22 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 10Today
19:55on time on time
20:13 / 20:14≈ on time ≈ on time
20:32 / 20:37≈ on time ≈ +1 min
20:50 / 20:52≈ on time ≈ +1 min
21:16 / 21:17≈ on time ≈ +2 min
21:27 / 21:29≈ on time ≈ +2 min
21:54 / 21:55≈ on time ≈ +2 min
22:06 / 22:07≈ on time ≈ +2 min
22:14on time +3 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 Nov— 22:290 min—
Wed 4 Nov— 22:140 min—
Mon 2 Nov— 22:22+3 min+4 min
Sun 1 NovHengelo 22:19+1 min+1 min
Sat 31 OctHengelo 22:42Partial coverage+3 min+3 min
Fri 30 Oct— 22:19No data—
Thu 29 Oct— 22:150 min—
Wed 28 Oct— 22:160 min—
Tue 27 Oct— 22:200 min—
Mon 26 Oct— 22:18No data—
Sun 25 OctDeventer 21:54No data—
Sat 24 OctDeventer 22:05No data—
Fri 23 Oct— 22:16+2 min+2 min
Thu 22 Oct— 22:160 min—
Wed 21 Oct— 22:15No data—
Tue 20 Oct— 22:20No data—
Mon 19 Oct— 21:280 min—
Sun 18 OctUtrecht Centraal 20:54+2 min+2 min
Sat 17 OctUtrecht Centraal 20:500 min—
Fri 16 Oct— 20:50No data—
Thu 15 Oct— 20:53No data—
Wed 14 Oct— 20:520 min—
Tue 13 Oct— 20:51No data—
Mon 12 Oct— 20:500 min—
Sun 11 OctHengelo 22:210 min—
Sat 10 OctAlmelo 22:16Partial coverage+1 min+1 min
Fri 9 Oct— 22:34+10 min+10 min
Thu 8 Oct— 22:18+2 min+4 min
Wed 7 Oct— 22:16+1 min+1 min
Tue 6 Oct— 22:150 min—