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

Gouda 18:13 → Alphen a/d Rijn 18:35 Mon, Tue, Wed, Thu, Fri 0 h 22 min · 7 stops R-net NS

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: Monday 18:13 from Gouda · Mon 9 Nov

Next departure 18:13 Monday · Gouda
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 3 full · 5 partial · 13 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 6 full · 5 partial · 38 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=1
  • 100% T n=1
  • 100% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 11 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:13on time on time
18:19≈ on time ≈ on time
18:21 / 18:23≈ on time ≈ on time
18:25≈ on time ≈ on time
18:27≈ on time ≈ on time
18:29 / 18:30≈ on time ≈ +1 min
18:35on 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
Fri 6 NovBoskoop 18:44Partial coverage+1 min+1 min
Thu 5 NovGouda 18:37No data—
Wed 4 NovGouda 18:37No data—
Tue 3 Nov— 18:340 min—
Mon 2 Nov— 18:37+2 min+2 min
Fri 30 OctBoskoop 18:44No data—
Thu 29 Oct— 18:37No data—
Wed 28 OctGouda 18:41Partial coverage+3 min+3 min
Tue 27 Oct— 18:380 min—
Mon 26 Oct— 18:37No data—
Fri 23 OctBoskoop 18:44No data—
Thu 22 OctBoskoop 18:44No data—
Wed 21 OctBoskoop 18:44No data—
Tue 20 OctBoskoop 18:44Partial coverage0 min—
Mon 19 OctBoskoop 18:44Partial coverage0 min—
Fri 16 OctBoskoop 18:44No data—
Thu 15 OctBoskoop 18:44No data—
Wed 14 OctBoskoop 18:42No data—
Tue 13 OctBoskoop 18:44No data—
Mon 12 OctBoskoop 18:44Partial coverage0 min—
Fri 9 OctBoskoop 18:44No data—
Thu 8 Oct— 18:350 min—
Wed 7 Oct— 18:36No data—
Tue 6 Oct— 18:360 min—
Mon 5 Oct— 18:350 min—
Fri 2 OctBoskoop 18:44No data—
Fri 25 SeptBoskoop 18:44No data—
Fri 18 SeptBoskoop 18:44No data—
Mon 14 SeptGouda 18:27No data—
Fri 11 SeptBoskoop 18:43No data—