Train NS 6860 Gouda Goverwelle → Den Haag Centraal

Gouda Goverwelle 18:34 → Den Haag Centraal 19:05 Mon, Tue, Wed, Thu 0 h 31 min · 8 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Thursday 19 November +1 min

Next service: Monday 18:34 from Gouda Goverwelle · Mon 23 Nov

Next departure 18:34 Monday · Gouda Goverwelle
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 9 full · 1 partial · 4 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 13 full · 2 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=4
  • 100% T n=4
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 15 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:34on time on time
18:38≈ on time ≈ on time
18:47≈ on time ≈ on time
18:50≈ on time ≈ on time
18:52≈ on time ≈ on time
18:57≈ on time ≈ +1 min
19:01≈ on time ≈ +1 min
19:05on time +1 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 Nov— 19:04+1 min—
Wed 18 NovGouda 19:07Partial coverage0 min—
Tue 17 Nov— 19:040 min—
Mon 16 Nov— 19:050 min—
Thu 12 Nov— 19:080 min—
Wed 11 Nov— 19:07+1 min—
Tue 10 Nov— 19:040 min—
Mon 9 Nov— 19:070 min—
Thu 5 Nov— 19:08No data—
Wed 4 Nov— 19:07No data—
Thu 29 Oct— 19:080 min+1 min
Wed 28 Oct— 19:11+1 min+1 min
Tue 27 Oct— 19:09No data—
Mon 26 Oct— 19:08No data—
Mon 19 OctGouda 19:060 min—
Thu 15 Oct— 19:08No data—
Wed 14 OctVoorburg 19:15Partial coverage0 min—
Tue 13 OctGouda 19:11No data—
Mon 12 OctGouda 19:07No data—
Thu 8 Oct— 19:060 min—
Tue 6 Oct— 19:060 min—
Mon 5 Oct— 19:030 min—
Thu 27 AugLansingerland-Zoetermeer 19:01No data—
Wed 26 AugVoorburg 19:14No data—
Tue 25 AugZoetermeer Oost 19:04No data—