Train NS 4060 Gouda – Uitgeest

Gouda 17:49 → Uitgeest 19:12 Daily 1 h 23 min · 18 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 17:49 from Gouda · Sun 8 Nov

Next departure 17:49 today · Gouda
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 16 full · 1 partial · 12 no data
On-time · 90 days
86%
19/22 runs under 3 min
RT coverage: 21 full · 1 partial · 66 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: +2 min

Last 30 days

Arrival delay at Uitgeest, 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 2 Nov Max en route +9 min · last fix heading to Woerden +9 min
  • Mon 5 Oct Max en route +6 min · last fix heading to Breukelen +5 min
  • Fri 6 Nov Max en route +3 min · last fix heading to Amsterdam Centraal +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 19
  • 3–10 min 14% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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:49on time on time
17:52≈ on time ≈ on time
18:02 / 18:03≈ on time ≈ +1 min
18:11≈ on time ≈ +1 min
18:20≈ on time ≈ +1 min
18:23≈ on time ≈ +1 min
18:25≈ on time ≈ +1 min
18:28≈ on time ≈ +2 min
18:32≈ on time ≈ +2 min
18:35≈ on time ≈ +2 min
18:41 / 18:42≈ on time ≈ +2 min
18:47 / 18:48≈ on time ≈ +2 min
18:55≈ on time ≈ +3 min
18:58≈ on time ≈ +3 min
19:00≈ on time ≈ +3 min
19:03 / 19:04≈ on time ≈ +3 min
19:07≈ on time ≈ +3 min
19:12on time +3 min

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 NovKrommenie-Assendelft 19:22Partial coverage0 min—
Fri 6 NovAmsterdam Centraal 19:14+3 min+3 min
Thu 5 NovBreukelen 19:23No data—
Wed 4 NovBreukelen 19:14No data—
Tue 3 NovBreukelen 19:14No data—
Mon 2 NovWoerden 19:39+9 min+9 min
Sun 1 NovWoerden 18:170 min—
Sat 31 OctKrommenie-Assendelft 19:220 min+1 min
Fri 30 OctAmsterdam Sloterdijk 19:19No data—
Thu 29 OctGouda Goverwelle 19:460 min+9 min
Wed 28 OctBreukelen 19:130 min—
Tue 27 OctWoerden 19:20No data—
Mon 26 OctWoerden 19:15+1 min+1 min
Sun 25 OctKrommenie-Assendelft 19:24No data—
Sat 24 OctKrommenie-Assendelft 19:270 min—
Fri 23 OctKrommenie-Assendelft 19:220 min—
Thu 22 OctAmsterdam Centraal 19:24No data—
Wed 21 OctAmsterdam Muiderpoort 19:14No data—
Tue 20 OctAmsterdam Centraal 19:150 min—
Mon 19 OctAmsterdam Centraal 18:570 min—
Sun 18 OctKrommenie-Assendelft 19:220 min+1 min
Sat 17 OctZaandijk Zaanse Schans 19:160 min—
Fri 16 OctZaandijk Zaanse Schans 19:15No data—
Thu 15 OctDuivendrecht 19:08No data—
Wed 14 OctZaandijk Zaanse Schans 19:09No data—
Tue 13 OctAmsterdam Muiderpoort 19:12No data—
Mon 12 OctAmsterdam Centraal 19:080 min—
Sun 11 OctWoerden 18:170 min—
Sat 10 OctKrommenie-Assendelft 19:23+2 min+2 min
Fri 9 OctAmsterdam Muiderpoort 19:15+2 min+2 min