Train NS 4082 Gouda – Uitgeest

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

Running now · updated 00:30

Heading to Uitgeest 0 min

Estimated arrival at Uitgeest 00:42 · 7 km/h

  1. Gouda23:19
  2. Breukelen23:41
  3. Amsterdam Bijlmer ArenA23:55
  4. Amsterdam Muiderpoort00:07
  5. Amsterdam Sloterdijk00:19
  6. Zaandijk Zaanse Schans00:30
  7. Uitgeest00:42

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

On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 0 no data
On-time · 90 days
97%
30/31 runs under 3 min
RT coverage: 31 full · 0 partial · 15 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 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 — +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 30
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 31 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
23:19on time on time
23:22≈ on time ≈ on time
23:31 / 23:33≈ on time ≈ on time
23:41≈ on time ≈ on time
23:50≈ on time ≈ on time
23:53≈ on time ≈ on time
23:55 / 23:57≈ on time ≈ on time
00:00≈ on time ≈ +1 min
00:04≈ on time ≈ +1 min
00:07≈ on time ≈ +1 min
00:12 / 00:13≈ on time ≈ +1 min
00:19≈ on time ≈ +1 min
00:24≈ on time ≈ +1 min
00:28≈ on time ≈ +1 min
00:30≈ on time ≈ +1 min
00:34≈ on time ≈ +1 min
00:38≈ on time ≈ on time
00:42on 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
Fri 6 Nov— 00:290 min—
Thu 5 Nov— 00:440 min—
Wed 4 Nov— 00:440 min—
Tue 3 Nov— 00:440 min—
Mon 2 Nov— 00:58+9 min+9 min
Sun 1 NovWoerden 23:480 min—
Sat 31 OctGouda 01:040 min—
Thu 29 Oct— 00:47+2 min+2 min
Wed 28 Oct— 00:480 min—
Tue 27 Oct— 00:440 min—
Mon 26 Oct— 00:430 min—
Sun 25 OctKrommenie-Assendelft 00:540 min—
Sat 24 Oct— 00:440 min—
Fri 23 Oct— 00:45+1 min+3 min
Thu 22 Oct— 00:500 min—
Wed 21 Oct— 00:460 min—
Tue 20 Oct— 00:480 min—
Sun 18 OctKrommenie-Assendelft 00:570 min+8 min
Sat 17 OctKoog aan de Zaan 00:420 min—
Fri 16 Oct— 01:120 min+15 min
Thu 15 Oct— 00:400 min—
Wed 14 Oct— 00:420 min—
Tue 13 Oct— 00:380 min—
Mon 12 Oct— 00:500 min—
Sun 11 OctWoerden 23:470 min—
Sat 10 Oct— 00:530 min—
Fri 9 Oct— 00:460 min—
Thu 8 Oct— 00:430 min—
Wed 7 Oct— 00:440 min—
Tue 6 Oct— 00:540 min+10 min