Train R-net NS 8651 Alphen a/d Rijn – Gouda

Alphen a/d Rijn 16:40 → Gouda 17:02 Daily 0 h 22 min · 7 stops R-net NS

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

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

Next departure 16:40 today · Alphen a/d Rijn
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 16 no data
On-time · 90 days
100%
29/29 runs under 3 min
RT coverage: 15 full · 14 partial · 59 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

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

  • Early 31% · 9
  • On time 69% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=6
  • 100% T n=5
  • 100% F n=4
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

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