Train NS 4049 Uitgeest – Gouda

Uitgeest 12:48 → Gouda 14:12 Daily 1 h 24 min · 18 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Gouda Goverwelle at 14:24 +2 min

  1. Uitgeest12:48
  2. Zaandijk Zaanse Schans12:59
  3. Amsterdam Sloterdijk13:11
  4. Amsterdam Amstel13:28
  5. Amsterdam Bijlmer ArenA13:34
  6. Gouda Goverwelle14:07
  7. Gouda14:12

Next service: tomorrow 12:48 from Uitgeest · Sun 8 Nov

Next departure 12:48 tomorrow · Uitgeest
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 16 full · 1 partial · 13 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 20 full · 1 partial · 68 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Gouda, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 24 Oct Max en route +12 min · last fix heading to Zoetermeer +12 min
  • Wed 7 Oct Max en route +8 min · last fix heading to Rotterdam Noord +8 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 90% · 19
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 75% W n=4
  • 100% T n=3
  • 100% F n=3
  • 80% 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, 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
12:48on time on time
12:52≈ on time ≈ on time
12:56≈ on time ≈ on time
12:59≈ on time ≈ on time
13:02≈ on time ≈ on time
13:05≈ on time ≈ on time
13:11 / 13:12≈ on time ≈ +1 min
13:17 / 13:19≈ on time ≈ +1 min
13:24≈ on time ≈ +1 min
13:28≈ on time ≈ +1 min
13:31≈ on time ≈ +1 min
13:34≈ on time ≈ +1 min
13:36≈ on time ≈ +1 min
13:40≈ on time ≈ +1 min
13:48≈ on time ≈ +1 min
13:56 / 13:58≈ on time ≈ +1 min
14:07 / 14:08≈ on time ≈ +2 min
14:12on time +2 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 NovGouda Goverwelle 14:24Partial coverage+2 min+5 min
Fri 6 NovRotterdam Noord 14:42No data—
Thu 5 NovRotterdam Noord 14:42No data—
Wed 4 NovRotterdam Noord 14:43+1 min—
Tue 3 NovRotterdam Noord 14:43No data—
Mon 2 NovRotterdam Noord 14:43No data—
Sun 1 NovRotterdam Noord 14:440 min—
Sat 31 OctRotterdam Noord 14:430 min—
Fri 30 OctRotterdam Noord 14:430 min—
Thu 29 OctRotterdam Noord 14:460 min—
Wed 28 OctRotterdam Noord 14:430 min—
Tue 27 OctRotterdam Noord 14:43No data—
Mon 26 OctRotterdam Noord 14:43No data—
Sun 25 OctZoetermeer 14:39No data—
Sat 24 OctZoetermeer 14:52+12 min+12 min
Fri 23 OctZoetermeer 14:43No data—
Thu 22 OctZoetermeer 14:380 min—
Wed 21 OctZoetermeer 14:38No data—
Tue 20 OctZoetermeer 14:41No data—
Mon 19 OctUtrecht Zuilen 14:120 min—
Sun 18 OctBreukelen 14:030 min—
Sat 17 OctGouda Goverwelle 14:220 min—
Fri 16 OctRotterdam Noord 14:430 min—
Thu 15 OctRotterdam Noord 14:43No data—
Wed 14 OctRotterdam Noord 14:440 min—
Tue 13 OctRotterdam Noord 14:43No data—
Mon 12 OctRotterdam Noord 14:43No data—
Sun 11 OctRotterdam Noord 14:43+1 min—
Sat 10 OctRotterdam Noord 14:430 min—
Fri 9 OctRotterdam Noord 14:430 min—