Train NS 6856 Gouda Goverwelle → Den Haag Centraal

Gouda Goverwelle 17:30 → Den Haag Centraal 18:02 Mon, Tue, Wed, Thu 0 h 32 min · 8 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Thursday 19 November 0 min

Next service: Monday 17:30 from Gouda Goverwelle · Mon 23 Nov

Next departure 17:30 Monday · Gouda Goverwelle
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 2 full · 11 partial · 3 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 3 full · 16 partial · 27 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: +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

Worst days

  • Tue 17 Nov Max en route +3 min · last fix heading to Voorburg +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=6
  • 75% T n=4
  • 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, 19 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
17:30on time on time
17:34 / 17:35— —
17:44— —
17:47— —
17:50— —
17:55— —
17:58— —
18:02— —

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 NovVoorburg 18:12Partial coverage0 min—
Wed 18 NovVoorburg 18:12Partial coverage0 min—
Tue 17 NovVoorburg 18:12Partial coverage+3 min+3 min
Mon 16 NovVoorburg 18:12Partial coverage+1 min+1 min
Thu 12 NovVoorburg 18:12Partial coverage0 min—
Wed 11 NovVoorburg 18:12Partial coverage+3 min+3 min
Tue 10 NovVoorburg 18:12Partial coverage0 min—
Mon 9 NovVoorburg 18:120 min—
Thu 5 NovVoorburg 18:09No data—
Wed 4 NovVoorburg 18:12Partial coverage0 min—
Tue 3 NovVoorburg 18:12No data—
Mon 2 NovVoorburg 18:12No data—
Thu 29 OctVoorburg 18:12Partial coverage0 min—
Wed 28 OctVoorburg 18:11Partial coverage0 min—
Tue 27 OctVoorburg 18:12Partial coverage0 min—
Mon 26 OctVoorburg 18:12+1 min—
Mon 19 OctVoorburg 18:140 min—
Thu 15 OctVoorburg 18:12No data—
Wed 14 OctVoorburg 18:12No data—
Tue 13 OctVoorburg 18:12No data—
Mon 12 OctVoorburg 18:12Partial coverage0 min—
Thu 8 OctVoorburg 18:13Partial coverage+1 min+2 min
Wed 7 OctVoorburg 18:12Partial coverage0 min—
Tue 6 OctVoorburg 18:12Partial coverage0 min—
Mon 5 OctVoorburg 18:12Partial coverage0 min—
Thu 1 OctVoorburg 18:12No data—
Wed 30 SeptVoorburg 18:12No data—
Tue 29 SeptVoorburg 18:12No data—
Mon 28 SeptVoorburg 18:12No data—
Thu 24 SeptDen Haag Ypenburg 18:10No data—