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

Gouda 06:13 → Alphen a/d Rijn 06: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 No data

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

Next departure 06:13 Monday · Gouda
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 1 full · 18 partial · 2 no data
On-time · 90 days
86%
44/51 runs under 3 min
RT coverage: 32 full · 19 partial · 13 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Mon 5 Oct Max en route +34 min · last fix heading to Boskoop +34 min
  • Tue 8 Sept Max en route +9 min · last fix heading to Boskoop +6 min
  • Tue 15 Sept Max en route +6 min · last fix heading to Boskoop +5 min
  • Wed 14 Oct Max en route +14 min · last fix heading to Boskoop +4 min
  • Fri 30 Oct Max en route +3 min · last fix heading to Boskoop +3 min

Distribution · 90 days

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

  • Early 25% · 13
  • On time 61% · 31
  • 3–10 min 12% · 6
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 91% M n=11
  • 64% T n=11
  • 88% W n=8
  • 100% T n=11
  • 90% F n=10
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 51 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
06:13on time on time
06:19≈ on time ≈ +1 min
06:21 / 06:23≈ on time ≈ +1 min
06:25≈ on time ≈ +2 min
06:27≈ on time ≈ +2 min
06:29 / 06:30≈ on time ≈ +2 min
06:35on time +3 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 06:44No data—
Thu 5 NovBoskoop 06:44Partial coverage0 min—
Wed 4 NovBoskoop 06:44Partial coverage0 min—
Tue 3 NovBoskoop 06:47Partial coverage+3 min+3 min
Mon 2 NovGouda 07:07No data—
Fri 30 OctBoskoop 06:47Partial coverage+3 min+3 min
Thu 29 OctBoskoop 06:46Partial coverage+2 min+2 min
Wed 28 OctBoskoop 06:45Partial coverage+1 min+1 min
Tue 27 OctBoskoop 06:46Partial coverage+2 min+2 min
Mon 26 OctBoskoop 06:45Partial coverage+1 min+1 min
Fri 23 OctBoskoop 06:47Partial coverage+3 min+3 min
Thu 22 OctBoskoop 06:45Partial coverage+1 min+1 min
Wed 21 OctBoskoop 06:45Partial coverage+1 min+2 min
Tue 20 OctBoskoop 06:47+3 min+3 min
Mon 19 OctBoskoop 06:45Partial coverage+1 min+1 min
Fri 16 OctBoskoop 06:45Partial coverage+1 min+1 min
Thu 15 OctBoskoop 06:45Partial coverage+1 min+1 min
Wed 14 OctBoskoop 06:48Partial coverage+4 min+14 min
Tue 13 OctBoskoop 06:45Partial coverage+1 min+1 min
Mon 12 OctBoskoop 06:46Partial coverage+2 min+2 min
Fri 9 OctBoskoop 06:44Partial coverage0 min—
Thu 8 OctBoskoop 06:44Partial coverage0 min—
Wed 7 OctBoskoop 06:44No data—
Tue 6 OctBoskoop 06:44No data—
Mon 5 OctBoskoop 09:42+34 min+34 min
Fri 2 OctBoskoop 18:06−3 min+3 min
Thu 1 OctBoskoop 18:06−1 min+5 min
Wed 30 SeptBoskoop 18:070 min+7 min
Tue 29 SeptBoskoop 19:09+3 min+5 min
Mon 28 SeptBoskoop 20:010 min+2 min