Train NS 8664 Gouda – Alphen a/d Rijn

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 19:28 from Gouda · Thu 5 Nov

Next departure 19:28 today · Gouda
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 10 full · 6 partial · 12 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 12 full · 6 partial · 38 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=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 100% S n=2
  • 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
19:28on time on time
19:34≈ on time ≈ on time
19:36 / 19:38≈ on time ≈ on time
19:40≈ on time ≈ on time
19:42≈ on time ≈ on time
19:44 / 19:45≈ on time ≈ on time
19:50on 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
Wed 4 Nov— 19:490 min—
Mon 2 Nov— 19:49No data—
Sun 1 NovBoskoop 19:59Partial coverage+1 min+1 min
Sat 31 OctBoskoop 20:01Partial coverage+2 min+2 min
Fri 30 Oct— 19:51No data—
Thu 29 Oct— 19:370 min—
Wed 28 Oct— 19:560 min—
Tue 27 Oct— 19:520 min—
Mon 26 OctBoskoop 19:54No data—
Sun 25 OctBoskoop 20:01No data—
Sat 24 OctBoskoop 20:00No data—
Fri 23 OctGouda 19:53Partial coverage+1 min+1 min
Thu 22 Oct— 19:58No data—
Wed 21 Oct— 19:52No data—
Tue 20 Oct— 19:510 min—
Mon 19 Oct— 19:52No data—
Sun 18 OctBoskoop 19:59Partial coverage0 min—
Sat 17 OctBoskoop 19:59No data—
Fri 16 OctBoskoop 19:59No data—
Thu 15 Oct— 19:510 min—
Wed 14 OctBoskoop 19:59No data—
Tue 13 Oct— 19:52No data—
Mon 12 Oct— 19:520 min—
Sun 11 OctBoskoop 19:59Partial coverage0 min—
Sat 10 OctBoskoop 19:59Partial coverage0 min—
Fri 9 Oct— 19:520 min—
Thu 8 Oct— 19:54+1 min+1 min
Wed 7 Oct— 19:520 min—
Tue 6 Oct— 19:510 min—
Mon 5 Oct— 19:510 min—