Train NS 6861 Den Haag Centraal – Gouda Goverwelle

Den Haag Centraal 16:28 → Gouda Goverwelle 16:59 Mon, Tue, Wed, Thu 0 h 31 min · 8 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Thursday 19 November 0 min

Next service: Monday 16:28 from Den Haag Centraal · Mon 23 Nov

Next departure 16:28 Monday · Den Haag Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 1 full · 12 partial · 3 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 3 full · 17 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Gouda Goverwelle, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 9 Nov Max en route +10 min · last fix heading to Gouda +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=5
  • 100% W n=5
  • 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, 20 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
16:28on time on time
16:32— —
16:35— —
16:40— —
16:42— —
16:45— —
16:55 / 16:56— —
16:59— —

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 NovGouda 17:09Partial coverage0 min+2 min
Wed 18 NovGouda 17:09Partial coverage0 min—
Tue 17 NovGouda 17:09Partial coverage0 min—
Mon 16 NovGouda 17:090 min—
Thu 12 NovGouda 17:09Partial coverage0 min—
Wed 11 NovGouda 17:09Partial coverage0 min—
Tue 10 NovGouda 17:09Partial coverage+2 min+2 min
Mon 9 NovGouda 17:19Partial coverage+8 min+10 min
Thu 5 NovGouda 17:09No data—
Wed 4 NovGouda 17:09Partial coverage0 min—
Tue 3 NovGouda 17:09No data—
Mon 2 NovGouda 17:28No data—
Thu 29 OctLansingerland-Zoetermeer 17:02Partial coverage0 min—
Wed 28 OctGouda 17:10Partial coverage0 min—
Tue 27 OctGouda 17:10Partial coverage0 min—
Mon 26 OctGouda 17:10Partial coverage0 min—
Mon 19 OctGouda 17:100 min—
Thu 15 OctGouda 17:11No data—
Wed 14 OctGouda 17:10No data—
Tue 13 OctGouda 17:100 min—
Mon 12 OctGouda 17:10Partial coverage0 min—
Thu 8 OctGouda 17:10Partial coverage0 min—
Wed 7 OctGouda 17:10Partial coverage0 min—
Tue 6 OctGouda 17:10Partial coverage0 min—
Mon 5 OctGouda 17:10Partial coverage0 min—
Thu 1 OctGouda 17:10No data—
Wed 30 SeptGouda 17:10No data—
Tue 29 SeptGouda 17:10No data—
Mon 28 SeptGouda 17:10No data—
Thu 24 SeptGouda 17:07No data—