Train NS 4087 Uitgeest – Gouda

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 22:18 from Uitgeest · Sat 7 Nov

Next departure 22:18 today · Uitgeest
On-time · 30 days
92%
24/26 runs under 3 min
RT coverage: 26 full · 0 partial · 2 no data
On-time · 90 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 18 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, 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 +17 min · last fix heading to — +17 min
  • Sun 18 Oct Max en route +16 min · last fix heading to Breukelen +16 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 27
  • 3–10 min 0% · 0
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
22:18on time on time
22:22≈ on time ≈ on time
22:26≈ on time ≈ on time
22:29≈ on time ≈ on time
22:32≈ on time ≈ on time
22:35≈ on time ≈ on time
22:41≈ on time ≈ on time
22:47 / 22:49≈ on time ≈ on time
22:54≈ on time ≈ on time
22:58≈ on time ≈ on time
23:01≈ on time ≈ on time
23:04≈ on time ≈ on time
23:06≈ on time ≈ on time
23:10≈ on time ≈ on time
23:18≈ on time ≈ on time
23:26 / 23:28≈ on time ≈ on time
23:37 / 23:38≈ on time ≈ on time
23: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:040 min—
Thu 5 Nov— 00:040 min—
Wed 4 Nov— 00:290 min+13 min
Mon 2 Nov— 00:37+17 min+17 min
Sun 1 NovRotterdam Noord 00:120 min—
Sat 31 OctBreukelen 23:320 min—
Fri 30 Oct— 00:050 min—
Thu 29 Oct— 00:050 min—
Wed 28 Oct— 00:050 min—
Tue 27 Oct— 00:160 min—
Mon 26 Oct— 00:050 min—
Sun 25 OctZoetermeer 00:080 min—
Sat 24 OctZaandam 00:08No data—
Fri 23 Oct— 00:040 min—
Thu 22 Oct— 00:060 min—
Wed 21 Oct— 00:12No data—
Tue 20 Oct— 00:100 min—
Mon 19 Oct— 23:320 min—
Sun 18 OctBreukelen 23:53+16 min+16 min
Sat 17 OctGouda Goverwelle 23:510 min—
Fri 16 Oct— 00:090 min+4 min
Thu 15 Oct— 00:070 min—
Wed 14 Oct— 00:050 min—
Tue 13 Oct— 00:050 min—
Mon 12 Oct— 00:060 min+5 min
Sun 11 OctRotterdam Noord 00:130 min—
Sat 10 Oct— 00:060 min—
Fri 9 Oct— 00:050 min—
Thu 8 Oct— 00:150 min+5 min
Wed 7 Oct— 00:050 min—