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

Gouda 18:21 → Alphen a/d Rijn 18:50 Daily 0 h 29 min · 7 stops R-net NS

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 18:21 from Gouda · Sat 7 Nov

Next departure 18:21 today · Gouda
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 3 full · 10 partial · 15 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 7 full · 10 partial · 52 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 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

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

  • Early 0% · 0
  • On time 100% · 17
  • 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=3
  • 100% W n=3
  • 100% 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, 17 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
18:21on time on time
18:26≈ on time ≈ on time
18:29 / 18:37≈ on time ≈ on time
18:40≈ on time ≈ on time
18:42≈ on time ≈ on time
18:44 / 18:45≈ on time ≈ on time
18:50on time on time

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 NovBoskoop 18:59Partial coverage0 min—
Thu 5 Nov— 18:49No data—
Wed 4 Nov— 18:490 min—
Tue 3 Nov— 18:53No data—
Mon 2 NovWaddinxveen 18:52Partial coverage+1 min+1 min
Sun 1 NovBoskoop 18:59Partial coverage0 min—
Sat 31 OctBoskoop 18:59No data—
Fri 30 OctBoskoop 18:59No data—
Wed 28 Oct— 18:52+1 min+1 min
Tue 27 Oct— 18:520 min—
Mon 26 Oct— 18:52No data—
Sun 25 OctBoskoop 18:59No data—
Sat 24 OctBoskoop 19:00No data—
Fri 23 OctBoskoop 18:59Partial coverage+1 min+1 min
Thu 22 OctBoskoop 19:07No data—
Wed 21 OctWaddinxveen Noord 18:54No data—
Tue 20 OctBoskoop 18:52Partial coverage0 min—
Mon 19 OctBoskoop Snijdelwijk 18:56No data—
Sun 18 OctBoskoop 18:59Partial coverage0 min—
Sat 17 OctBoskoop 18:59No data—
Fri 16 OctBoskoop 18:59No data—
Thu 15 OctWaddinxveen Triangel 18:52No data—
Wed 14 OctBoskoop 18:59No data—
Tue 13 OctWaddinxveen Noord 18:52No data—
Mon 12 OctBoskoop 18:59Partial coverage0 min—
Sun 11 OctBoskoop 18:59Partial coverage0 min—
Sat 10 OctBoskoop 18:59Partial coverage0 min—
Fri 9 OctWaddinxveen Triangel 18:51Partial coverage0 min—
Thu 8 Oct— 18:510 min—
Wed 7 Oct— 18:510 min—