Train NS 8662 Gouda – Alphen a/d Rijn

Gouda 18:58 → Alphen a/d Rijn 19:20 Daily 0 h 22 min · 7 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 19:22 0 min

  1. Gouda18:58
  2. Waddinxveen Triangel19:04
  3. Waddinxveen19:06
  4. Waddinxveen Noord19:10
  5. Boskoop Snijdelwijk19:12
  6. Boskoop19:14
  7. Alphen a/d Rijn19:20

Next service: tomorrow 18:58 from Gouda · Tue 10 Nov

Next departure 18:58 tomorrow · Gouda
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 7 full · 6 partial · 14 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 11 full · 7 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Alphen a/d Rijn, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
18:58on time on time
19:04≈ on time ≈ on time
19:06 / 19:08≈ on time ≈ on time
19:10≈ on time ≈ on time
19:12≈ on time ≈ on time
19:14 / 19:15≈ on time ≈ on time
19:20on 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
Mon 9 Nov— 19:220 min—
Sun 8 NovBoskoop 19:29Partial coverage+1 min+1 min
Sat 7 NovBoskoop 19:29Partial coverage0 min—
Fri 6 Nov— 19:230 min+1 min
Thu 5 Nov— 19:19No data—
Wed 4 Nov— 19:190 min—
Sun 1 NovBoskoop 19:29Partial coverage0 min—
Sat 31 OctBoskoop 19:30Partial coverage0 min—
Fri 30 Oct— 19:21No data—
Thu 29 Oct— 19:22+1 min—
Wed 28 Oct— 19:370 min—
Tue 27 Oct— 19:22No data—
Mon 26 Oct— 19:280 min—
Sun 25 OctBoskoop 19:30No data—
Sat 24 OctBoskoop 19:30No data—
Fri 23 OctBoskoop 19:29Partial coverage0 min—
Thu 22 Oct— 19:26No data—
Wed 21 Oct— 19:22No data—
Mon 19 Oct— 19:22No data—
Sun 18 OctBoskoop 19:29Partial coverage0 min—
Sat 17 OctBoskoop 19:29No data—
Fri 16 OctBoskoop 19:29No data—
Thu 15 Oct— 19:24No data—
Wed 14 OctBoskoop 19:29No data—
Tue 13 Oct— 19:22No data—
Mon 12 Oct— 19:230 min—
Sun 11 OctBoskoop 19:29No data—
Sat 10 OctBoskoop 19:30Partial coverage+1 min+1 min
Fri 9 Oct— 19:210 min—
Thu 8 Oct— 19:210 min—