Train NS 6095 Den Haag Centraal – Gouda Goverwelle

Den Haag Centraal 00:16 → Gouda Goverwelle 00:48 Daily 0 h 32 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 00:49 0 min

  1. Den Haag Centraal00:16
  2. Voorburg00:20
  3. Den Haag Ypenburg00:23
  4. Zoetermeer Oost00:31
  5. Lansingerland-Zoetermeer00:33
  6. Gouda00:43
  7. Gouda Goverwelle00:48

Next service: Monday 00:16 from Den Haag Centraal · Mon 9 Nov

Next departure 00:16 Monday · Den Haag Centraal
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 3 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 12 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: 0 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=2
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 26 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
00:16on time on time
00:20≈ on time ≈ on time
00:23≈ on time ≈ on time
00:28≈ on time ≈ on time
00:31≈ on time ≈ on time
00:33≈ on time ≈ on time
00:43 / 00:45≈ on time ≈ on time
00:48on time on time

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
Sat 7 Nov— 00:490 min+2 min
Fri 6 Nov— 00:49No data—
Thu 5 Nov— 00:490 min—
Wed 4 Nov— 00:490 min—
Tue 3 Nov— 00:490 min—
Mon 2 NovGouda 00:590 min—
Fri 30 Oct— 00:490 min—
Thu 29 Oct— 00:510 min—
Wed 28 Oct— 00:500 min—
Tue 27 Oct— 00:490 min—
Mon 26 OctGouda 00:590 min—
Sun 25 Oct— 00:500 min—
Fri 23 Oct— 00:530 min—
Thu 22 Oct— 00:530 min—
Wed 21 Oct— 00:530 min—
Tue 20 Oct— 01:140 min—
Mon 19 OctBreukelen 02:590 min—
Sun 18 OctGouda 00:590 min—
Sat 17 Oct— 00:490 min—
Fri 16 Oct— 00:49No data—
Thu 15 Oct— 00:490 min—
Wed 14 Oct— 00:500 min—
Tue 13 Oct— 00:490 min—
Mon 12 OctGouda 00:59No data—
Sun 11 Oct— 00:490 min—
Sat 10 Oct— 00:490 min—
Thu 8 Oct— 00:500 min—
Wed 7 Oct— 00:53+1 min+3 min
Tue 6 Oct— 00:490 min—
Mon 5 OctGouda 00:59No data—