Train NS 6818 Gouda Goverwelle – Den Haag Centraal

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

It does not run today

Last recorded run: Thursday 19 November +6 min

Next service: Monday 08:00 from Gouda Goverwelle · Mon 23 Nov

Next departure 08:00 Monday · Gouda Goverwelle
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 2 full · 12 partial · 2 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 3 full · 15 partial · 29 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

Worst days

  • Thu 19 Nov Max en route +6 min · last fix heading to Voorburg +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=6
  • 67% T n=3
  • — 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, 18 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
08:00on time on time
08:04 / 08:05— —
08:14— —
08:17— —
08:20— —
08:25— —
08:28— —
08:32— —

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 08:48Partial coverage+6 min+6 min
Wed 18 NovVoorburg 08:43Partial coverage0 min—
Tue 17 NovVoorburg 08:43Partial coverage0 min—
Mon 16 NovVoorburg 08:44Partial coverage+2 min+2 min
Thu 12 NovVoorburg 08:43Partial coverage+1 min+1 min
Wed 11 NovVoorburg 08:43Partial coverage0 min—
Tue 10 NovVoorburg 08:44Partial coverage+1 min+2 min
Mon 9 NovVoorburg 08:43Partial coverage0 min—
Thu 5 NovVoorburg 08:43No data—
Wed 4 NovVoorburg 08:42Partial coverage0 min—
Tue 3 NovZoetermeer Oost 09:340 min—
Mon 2 NovVoorburg 08:44Partial coverage0 min—
Thu 29 OctVoorburg 08:48Partial coverage0 min—
Wed 28 OctVoorburg 08:430 min—
Tue 27 OctVoorburg 08:43No data—
Mon 26 OctVoorburg 08:43Partial coverage0 min—
Mon 19 OctVoorburg 08:480 min—
Thu 15 OctVoorburg 08:44No data—
Wed 14 OctVoorburg 08:44Partial coverage0 min—
Tue 13 OctVoorburg 08:45No data—
Mon 12 OctVoorburg 08:46No data—
Thu 8 OctVoorburg 08:42No data—
Wed 7 OctVoorburg 08:44Partial coverage0 min—
Tue 6 OctVoorburg 08:43Partial coverage0 min—
Mon 5 OctVoorburg 08:44No data—
Thu 1 OctVoorburg 08:42No data—
Wed 30 SeptVoorburg 08:42No data—
Tue 29 SeptVoorburg 08:43No data—
Mon 28 SeptVoorburg 08:43No data—
Thu 24 SeptVoorburg 08:43No data—