Train NS 8671 Alphen a/d Rijn – Gouda

Alphen a/d Rijn 21:40 → Gouda 22:02 Daily 0 h 22 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 21:40 from Alphen a/d Rijn · Sat 7 Nov

Next departure 21:40 today · Alphen a/d Rijn
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 11 full · 4 partial · 13 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 15 full · 4 partial · 29 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 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

  • Thu 29 Oct Max en route +15 min · last fix heading to — +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
21:40on time on time
21:44 / 21:45≈ on time ≈ +1 min
21:47≈ on time ≈ +1 min
21:49≈ on time ≈ +1 min
21:52≈ on time ≈ +1 min
21:55≈ on time ≈ +1 min
22:02on time +1 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
Fri 6 Nov— 22:040 min+1 min
Thu 5 Nov— 22:04No data—
Wed 4 Nov— 22:040 min—
Mon 2 Nov— 22:04+1 min+1 min
Sun 1 NovWaddinxveen Triangel 22:09Partial coverage0 min—
Sat 31 OctWaddinxveen Triangel 22:09No data—
Fri 30 Oct— 22:06No data—
Thu 29 Oct— 22:17+15 min+15 min
Wed 28 Oct— 22:060 min—
Tue 27 Oct— 22:040 min—
Mon 26 Oct— 22:04No data—
Sun 25 OctWaddinxveen Triangel 22:13No data—
Sat 24 OctWaddinxveen Triangel 22:09No data—
Fri 23 Oct— 22:08+2 min+2 min
Thu 22 Oct— 22:04No data—
Wed 21 Oct— 22:04No data—
Tue 20 Oct— 22:060 min—
Mon 19 Oct— 22:03No data—
Sun 18 OctWaddinxveen Triangel 22:10Partial coverage+1 min—
Sat 17 OctWaddinxveen Triangel 22:09No data—
Fri 16 Oct— 22:07+1 min+2 min
Thu 15 Oct— 22:04No data—
Wed 14 Oct— 22:04No data—
Tue 13 Oct— 22:04No data—
Mon 12 Oct— 22:040 min—
Sun 11 OctWaddinxveen Triangel 22:09Partial coverage0 min—
Sat 10 OctWaddinxveen Triangel 22:09Partial coverage0 min—
Fri 9 Oct— 22:060 min+1 min
Thu 8 Oct— 22:040 min—
Wed 7 Oct— 22:040 min—