Train NS 8675 Alphen a/d Rijn – Gouda

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

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

Next service: today 22:40 from Alphen a/d Rijn · Thu 5 Nov

Next departure 22:40 today · Alphen a/d Rijn
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 9 full · 2 partial · 14 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 11 full · 2 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: +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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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