Train NS 8667 Alphen a/d Rijn – Gouda

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 20:40 from Alphen a/d Rijn · Fri 6 Nov

Next departure 20:40 today · Alphen a/d Rijn
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 9 full · 4 partial · 14 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 12 full · 4 partial · 32 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: +2 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

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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