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

Gouda 07:58 → Alphen a/d Rijn 08:20 Daily 0 h 22 min · 7 stops R-net NS

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 07:58 from Gouda · Fri 6 Nov

Full trip card
Next departure 07:58 today · Gouda
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 0 full · 14 partial · 15 no data
On-time · 90 days
85%
22/26 runs under 3 min
RT coverage: 11 full · 15 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +4 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 24 Oct Max en route +6 min · last fix heading to Boskoop +6 min
  • Wed 23 Sept Max en route +6 min · last fix heading to Waddinxveen Triangel +5 min
  • Sat 17 Oct Max en route +5 min · last fix heading to Boskoop +5 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Boskoop +5 min

Distribution · 90 days

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

  • Early 27% · 7
  • On time 58% · 15
  • 3–10 min 15% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 75% W n=4
  • 100% T n=3
  • 100% F n=3
  • 50% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 26 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
Gouda
07:58on time +1 min
Waddinxveen Triangel
08:04≈ on time ≈ on time
Waddinxveen
08:06 / 08:08≈ 1 min early ≈ on time
Waddinxveen Noord
08:10≈ 1 min early ≈ on time
Boskoop Snijdelwijk
08:12≈ 1 min early ≈ +1 min
Boskoop
08:14 / 08:15≈ 1 min early ≈ +1 min
Alphen a/d Rijn
08:202 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
Thu 5 NovBoskoop 08:32No data—
Wed 4 NovBoskoop 08:29Partial coverage+2 min+2 min
Tue 3 NovBoskoop 08:39No data—
Mon 2 NovBoskoop 08:29No data—
Sun 1 NovBoskoop 08:30Partial coverage+1 min+1 min
Sat 31 OctBoskoop 08:30Partial coverage0 min—
Fri 30 OctBoskoop 08:30No data—
Thu 29 Oct— 08:10No data—
Wed 28 OctBoskoop 08:29Partial coverage0 min—
Tue 27 OctBoskoop 08:30Partial coverage0 min—
Mon 26 OctBoskoop 08:30Partial coverage0 min—
Sun 25 OctBoskoop 08:29No data—
Sat 24 OctBoskoop 08:34Partial coverage+6 min+6 min
Fri 23 OctBoskoop 08:29No data—
Thu 22 OctBoskoop 08:30No data—
Wed 21 OctBoskoop 08:29No data—
Tue 20 OctBoskoop 08:30Partial coverage0 min—
Mon 19 OctBoskoop 08:29No data—
Sun 18 OctBoskoop 08:29Partial coverage0 min—
Sat 17 OctBoskoop 08:34Partial coverage+5 min+5 min
Fri 16 OctBoskoop 08:29No data—
Thu 15 OctBoskoop 08:30No data—
Wed 14 OctBoskoop 08:30No data—
Tue 13 OctBoskoop Snijdelwijk 08:31No data—
Mon 12 OctBoskoop 08:30No data—
Sun 11 OctBoskoop 08:30Partial coverage+1 min+1 min
Sat 10 OctBoskoop 08:30Partial coverage+1 min+1 min
Fri 9 OctBoskoop 08:30Partial coverage+1 min—
Thu 8 OctBoskoop 08:29Partial coverage0 min—
Wed 7 OctBoskoop 08:29No data—