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

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

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 17:58 from Gouda · Tue 10 Nov

Next departure 17:58 today · Gouda
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 18 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 0 full · 17 partial · 69 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=2
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

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