Train NS 1770 Enschede – Den Haag Centraal

Enschede 18:45 → Den Haag Centraal 21:05 Daily 2 h 20 min · 9 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 21:04 0 min

  1. Enschede18:45
  2. Hengelo18:52
  3. Deventer19:30
  4. Apeldoorn19:43
  5. Amersfoort Centraal20:08
  6. Gouda20:46
  7. Den Haag Centraal21:05

Next service: tomorrow 18:45 from Enschede · Tue 10 Nov

Next departure 18:45 tomorrow · Enschede
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 21 full · 3 partial · 6 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 27 full · 3 partial · 38 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: +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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 30
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 100% W n=4
  • 100% T n=4
  • 100% F n=3
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 30 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
18:45on time on time
18:52 / 18:53≈ on time ≈ on time
19:04 / 19:05≈ on time ≈ on time
19:30 / 19:33≈ on time ≈ +1 min
19:43 / 19:44≈ on time ≈ +1 min
20:08 / 20:10≈ on time ≈ +1 min
20:23 / 20:28≈ on time ≈ +1 min
20:46 / 20:47≈ on time ≈ +2 min
21: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
Mon 9 Nov— 21:040 min—
Sun 8 NovLansingerland-Zoetermeer 21:09+1 min—
Sat 7 NovLansingerland-Zoetermeer 21:13+3 min+4 min
Fri 6 NovEnschede 21:04Partial coverage+1 min+2 min
Thu 5 Nov— 21:070 min—
Wed 4 Nov— 21:07+1 min+2 min
Tue 3 Nov— 21:05No data—
Mon 2 Nov— 19:120 min—
Sun 1 NovGouda 21:040 min—
Sat 31 OctGouda 21:01Partial coverage0 min—
Fri 30 OctHengelo 21:06No data—
Thu 29 Oct— 21:09+1 min+2 min
Wed 28 Oct— 21:110 min—
Tue 27 Oct— 21:070 min—
Mon 26 OctApeldoorn 21:35Partial coverage0 min—
Sun 25 OctGouda 21:11No data—
Sat 24 OctGouda 21:050 min—
Fri 23 OctAlmelo 21:11+3 min+3 min
Thu 22 OctEnschede 21:110 min—
Wed 21 Oct— 21:070 min—
Tue 20 OctEnschede 21:330 min—
Mon 19 Oct— 20:480 min—
Sun 18 OctAmersfoort Centraal 20:31+2 min+2 min
Sat 17 OctGouda 21:010 min—
Fri 16 Oct— 21:06No data—
Thu 15 Oct— 21:09No data—
Wed 14 Oct— 21:06No data—
Tue 13 Oct— 21:150 min—
Mon 12 Oct— 21:060 min—
Sun 11 OctGouda 21:060 min—