Train NS 4034 Gouda – Uitgeest

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

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 11:19 from Gouda · Mon 9 Nov

Next departure 11:19 today · Gouda
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 13 full · 2 partial · 14 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 19 full · 2 partial · 67 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

  • Thu 8 Oct Max en route +5 min · last fix heading to Krommenie-Assendelft +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=1
  • 100% T n=1
  • 100% W n=3
  • 67% T n=3
  • 100% F n=3
  • 100% S n=6
  • 100% S n=4

Stops and timetable

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

Last 90 days, 21 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
11:19on time on time
11:22≈ on time ≈ on time
11:31 / 11:33≈ on time ≈ on time
11:41≈ on time ≈ +1 min
11:50≈ on time ≈ +1 min
11:53≈ on time ≈ +1 min
11:55≈ on time ≈ +1 min
11:58≈ on time ≈ +1 min
12:02≈ on time ≈ +1 min
12:05≈ on time ≈ +2 min
12:11 / 12:13≈ on time ≈ +2 min
12:18≈ on time ≈ +2 min
12:25≈ on time ≈ +2 min
12:28≈ on time ≈ +2 min
12:30≈ on time ≈ +2 min
12:33 / 12:34≈ on time ≈ +2 min
12:37≈ on time ≈ +3 min
12:42on 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
Sun 8 NovKrommenie-Assendelft 12:49Partial coverage0 min—
Sat 7 NovKrommenie-Assendelft 12:52Partial coverage0 min—
Fri 6 NovKrommenie-Assendelft 12:49No data—
Thu 5 NovKrommenie-Assendelft 12:54No data—
Wed 4 NovKrommenie-Assendelft 12:52+3 min+3 min
Tue 3 NovKrommenie-Assendelft 12:52No data—
Mon 2 NovKrommenie-Assendelft 12:58No data—
Sun 1 NovWoerden 11:480 min—
Sat 31 OctKrommenie-Assendelft 12:520 min—
Fri 30 OctKrommenie-Assendelft 12:520 min—
Thu 29 OctKrommenie-Assendelft 12:530 min—
Wed 28 OctKrommenie-Assendelft 12:530 min—
Tue 27 OctKrommenie-Assendelft 12:52No data—
Mon 26 OctKrommenie-Assendelft 12:58No data—
Sun 25 OctKrommenie-Assendelft 12:52No data—
Sat 24 OctKrommenie-Assendelft 12:52+1 min—
Fri 23 OctKrommenie-Assendelft 12:52No data—
Thu 22 OctKrommenie-Assendelft 12:550 min—
Wed 21 OctKrommenie-Assendelft 12:54No data—
Tue 20 OctKrommenie-Assendelft 12:59No data—
Mon 19 OctKrommenie-Assendelft 12:530 min—
Sun 18 OctKrommenie-Assendelft 12:54+2 min+4 min
Sat 17 OctZaandijk Zaanse Schans 12:450 min—
Fri 16 OctZaandijk Zaanse Schans 12:450 min—
Thu 15 OctZaandijk Zaanse Schans 12:49No data—
Wed 14 OctZaandijk Zaanse Schans 12:49No data—
Tue 13 OctZaandijk Zaanse Schans 12:45No data—
Mon 12 OctZaandijk Zaanse Schans 12:45No data—
Sun 11 OctWoerden 11:470 min—
Sat 10 OctKrommenie-Assendelft 12:54+3 min+3 min