Train NS 8674 Gouda – Alphen a/d Rijn

Gouda 21:58 → Alphen a/d Rijn 22:20 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 21:58 from Gouda · Thu 5 Nov

Next departure 21:58 today · Gouda
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 9 full · 4 partial · 14 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 11 full · 4 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

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

  • Early 0% · 0
  • On time 100% · 15
  • 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=1
  • 100% W n=3
  • 100% T n=2
  • 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, 15 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:58on time on time
22:04≈ on time ≈ +1 min
22:06 / 22:08≈ on time ≈ +1 min
22:10≈ on time ≈ +1 min
22:12≈ on time ≈ +1 min
22:14 / 22:15≈ on time ≈ +2 min
22:20on 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
Wed 4 Nov— 22:24+2 min+2 min
Sun 1 NovBoskoop 22:29Partial coverage0 min—
Sat 31 OctBoskoop 22:29No data—
Fri 30 Oct— 22:21No data—
Thu 29 Oct— 22:24+2 min+2 min
Wed 28 Oct— 22:21No data—
Tue 27 Oct— 22:24No data—
Mon 26 Oct— 22:210 min—
Sun 25 OctBoskoop 22:30No data—
Sat 24 OctBoskoop 22:29No data—
Fri 23 Oct— 22:26+3 min+3 min
Thu 22 Oct— 22:22No data—
Wed 21 Oct— 22:22No data—
Tue 20 Oct— 22:28No data—
Mon 19 Oct— 22:22No data—
Sun 18 OctBoskoop 22:29Partial coverage0 min—
Sat 17 OctBoskoop 22:29No data—
Fri 16 Oct— 22:22+1 min+1 min
Thu 15 Oct— 22:09No data—
Wed 14 Oct— 22:210 min—
Tue 13 Oct— 22:22No data—
Mon 12 Oct— 22:21No data—
Sun 11 OctBoskoop 22:30Partial coverage+1 min+1 min
Sat 10 OctWaddinxveen Triangel 22:22Partial coverage0 min—
Fri 9 Oct— 22:21+1 min+1 min
Thu 8 Oct— 22:220 min—
Wed 7 Oct— 22:220 min—
Tue 6 Oct— 22:210 min—
Mon 5 Oct— 22:210 min—
Sun 4 OctBoskoop 22:30No data—