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

Gouda 05:30 → Alphen a/d Rijn 05:51 Mon, Tue, Wed, Thu, Fri 0 h 21 min · 7 stops R-net NS

✓ Today’s run finished

Today, last fix heading to Boskoop at 05:59 No data

  1. Gouda05:30
  2. Waddinxveen Triangel05:36
  3. Waddinxveen05:39
  4. Waddinxveen Noord05:41
  5. Boskoop Snijdelwijk05:43
  6. Boskoop05:45
  7. Alphen a/d Rijn05:51

Next service: Monday 05:30 from Gouda · Mon 9 Nov

Next departure 05:30 Monday · Gouda
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 0 full · 18 partial · 4 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 0 full · 19 partial · 45 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

  • Thu 5 Nov Max en route +3 min · last fix heading to Boskoop +3 min
  • Thu 15 Oct Max en route +3 min · last fix heading to Boskoop +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
05:30on time on time
05:36— —
05:39— —
05:41— —
05:43— —
05:45 / 05:46— —
05:51— —

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 05:59No data—
Thu 5 NovBoskoop 06:03Partial coverage+3 min+3 min
Wed 4 Nov— 05:53No data—
Tue 3 NovBoskoop 05:59Partial coverage0 min—
Mon 2 NovBoskoop 06:03No data—
Fri 30 OctBoskoop 06:02Partial coverage+2 min+2 min
Thu 29 OctBoskoop 06:02Partial coverage+2 min+2 min
Wed 28 OctBoskoop 06:01Partial coverage0 min—
Tue 27 OctBoskoop 06:02Partial coverage+2 min+2 min
Mon 26 OctBoskoop 06:01Partial coverage0 min—
Fri 23 OctBoskoop 06:00No data—
Thu 22 OctBoskoop 06:00Partial coverage0 min—
Wed 21 OctBoskoop 06:00Partial coverage0 min—
Tue 20 OctBoskoop 06:01Partial coverage+1 min+1 min
Mon 19 OctBoskoop 06:01Partial coverage+1 min+1 min
Fri 16 OctBoskoop 06:00Partial coverage0 min—
Thu 15 OctBoskoop 06:03Partial coverage+3 min+3 min
Wed 14 OctBoskoop 06:00Partial coverage0 min—
Tue 13 OctBoskoop 06:01Partial coverage+1 min+1 min
Mon 12 OctBoskoop 06:02Partial coverage+3 min+3 min
Fri 9 OctBoskoop 06:02Partial coverage+2 min+2 min
Thu 8 OctBoskoop 06:00Partial coverage0 min—
Wed 7 OctBoskoop 06:00No data—
Tue 6 OctBoskoop 06:00Partial coverage0 min—
Mon 5 OctBoskoop 06:01No data—
Fri 2 OctBoskoop 06:01No data—
Thu 1 OctBoskoop 06:01No data—
Wed 30 SeptBoskoop 06:00No data—
Tue 29 SeptBoskoop 06:01No data—
Mon 28 SeptBoskoop 06:01No data—