Train NS 6857 Den Haag Centraal – Gouda Goverwelle

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

Running now · updated 15:29

Heading to Gouda Goverwelle 0 min

Estimated arrival at Gouda Goverwelle 15:59 · 78 km/h

  1. Den Haag Centraal15:28
  2. Voorburg15:32
  3. Den Haag Ypenburg15:35
  4. Zoetermeer Oost15:42
  5. Lansingerland-Zoetermeer15:45
  6. Gouda15:55
  7. Gouda Goverwelle15:59

Today it is running no worse than usual: typical arrival delay is 0 min; 80% of the last 10 runs arrived on time.

On-time · 30 days
80%
8/10 runs under 3 min
RT coverage: 1 full · 9 partial · 5 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 2 full · 16 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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 +8 min · last fix heading to Gouda +7 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Gouda +3 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 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=4
  • 83% W n=6
  • 100% 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 10Today
15:28on time +1 min
15:32— —
15:35— —
15:40— —
15:42— —
15:45— —
15:55 / 15:56— —
15: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
Wed 18 NovDen Haag Centraal 15:24Partial coverage0 min—
Tue 17 NovGouda 16:090 min—
Mon 16 NovGouda 16:09Partial coverage0 min—
Thu 12 NovGouda 16:09Partial coverage0 min—
Wed 11 NovGouda 16:09Partial coverage0 min—
Tue 10 NovGouda 16:12Partial coverage+3 min+3 min
Mon 9 NovGouda 16:17Partial coverage+7 min+8 min
Thu 5 NovGouda 16:10No data—
Wed 4 NovGouda 16:13Partial coverage+3 min+5 min
Tue 3 NovGouda 16:09No data—
Mon 2 NovGouda 16:09No data—
Thu 29 Oct— 16:00No data—
Wed 28 OctGouda 16:13Partial coverage0 min—
Tue 27 OctGouda 16:10Partial coverage0 min—
Mon 26 OctGouda 16:10No data—
Mon 19 OctGouda 16:110 min—
Thu 15 OctGouda 16:10Partial coverage0 min—
Wed 14 OctGouda 16:10Partial coverage0 min—
Tue 13 OctGouda 16:10No data—
Mon 12 OctGouda 16:11Partial coverage+1 min+2 min
Thu 8 OctGouda 16:10Partial coverage0 min—
Wed 7 OctGouda 16:10Partial coverage0 min—
Tue 6 OctGouda 16:11Partial coverage+1 min+1 min
Mon 5 OctGouda 16:10Partial coverage0 min—
Thu 1 OctGouda 16:10No data—
Wed 30 SeptGouda 16:10No data—
Tue 29 SeptGouda 16:11No data—
Mon 28 SeptGouda 16:10No data—
Thu 24 SeptGouda 16:11No data—
Wed 23 SeptGouda 16:10No data—