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

Gouda 06:58 → Alphen a/d Rijn 07:20 Mon, Tue, Wed, Thu, Fri, Sat 0 h 22 min · 7 stops R-net NS

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 06:58 from Gouda · Sat 7 Nov

Next departure 06:58 today · Gouda
On-time · 30 days
81%
17/21 runs under 3 min
RT coverage: 0 full · 21 partial · 4 no data
On-time · 90 days
83%
19/23 runs under 3 min
RT coverage: 0 full · 23 partial · 53 no data
Typical delay
+1min
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

  • Sat 17 Oct Max en route +13 min · last fix heading to Boskoop +13 min
  • Sat 24 Oct Max en route +12 min · last fix heading to Boskoop +12 min
  • Wed 14 Oct Max en route +3 min · last fix heading to Boskoop +3 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Boskoop +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 19
  • 3–10 min 9% · 2
  • 10–30 min 9% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 50% W n=4
  • 100% T n=3
  • 100% F n=4
  • 50% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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:58on time on time
07:04— —
07:06 / 07:08— —
07:10— —
07:12— —
07:14 / 07:15— —
07:20— —

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 07:30No data—
Thu 5 Nov— 07:19No data—
Wed 4 NovBoskoop 07:32Partial coverage+3 min+3 min
Tue 3 NovBoskoop 07:29Partial coverage+1 min+2 min
Mon 2 NovBoskoop 07:29No data—
Sat 31 OctBoskoop 07:29Partial coverage0 min—
Fri 30 OctBoskoop 07:31Partial coverage+2 min+3 min
Thu 29 Oct— 07:10No data—
Wed 28 OctBoskoop 07:31Partial coverage0 min—
Tue 27 OctBoskoop 07:34Partial coverage0 min—
Mon 26 OctBoskoop 07:30Partial coverage+1 min+1 min
Sat 24 OctBoskoop 07:40Partial coverage+12 min+12 min
Fri 23 OctBoskoop 07:30Partial coverage0 min—
Thu 22 OctBoskoop 07:30Partial coverage+1 min—
Wed 21 OctBoskoop 07:29Partial coverage0 min—
Tue 20 OctBoskoop 07:30Partial coverage+1 min—
Mon 19 OctBoskoop 07:31Partial coverage+2 min+2 min
Sat 17 OctBoskoop 07:41Partial coverage+13 min+13 min
Fri 16 OctBoskoop 07:29Partial coverage0 min—
Thu 15 OctBoskoop 07:29Partial coverage+1 min—
Wed 14 OctBoskoop 07:32Partial coverage+3 min+3 min
Tue 13 OctBoskoop 07:30Partial coverage0 min—
Mon 12 OctBoskoop 07:32Partial coverage+1 min+1 min
Sat 10 OctBoskoop 07:30Partial coverage+1 min+1 min
Fri 9 OctBoskoop 07:30Partial coverage+1 min—
Thu 8 OctBoskoop 07:30Partial coverage+1 min—
Wed 7 OctBoskoop 07:29No data—
Tue 6 OctBoskoop 07:30Partial coverage+1 min+1 min
Mon 5 OctBoskoop 07:32No data—
Sat 3 OctBoskoop 07:30No data—