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

Alphen a/d Rijn 09:55 → Gouda 10:17 Mon, Tue, Wed, Thu, Fri 0 h 22 min · 7 stops R-net NS

✓ Today’s run finished

Today, last fix heading to Waddinxveen Triangel at 10:24 No data

  1. Alphen a/d Rijn09:55
  2. Boskoop09:59
  3. Boskoop Snijdelwijk10:02
  4. Waddinxveen Noord10:04
  5. Waddinxveen10:07
  6. Waddinxveen Triangel10:10
  7. Gouda10:17

Next service: tomorrow 09:55 from Alphen a/d Rijn · Fri 6 Nov

Next departure 09:55 tomorrow · Alphen a/d Rijn
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 13 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 53 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Gouda, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 9 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
09:55on time on time
09:59 / 10:00— —
10:02— —
10:04— —
10:07— —
10:10— —
10:17— —

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 NovWaddinxveen Triangel 10:24No data—
Wed 4 NovWaddinxveen Triangel 10:24Partial coverage0 min—
Tue 3 NovWaddinxveen Triangel 10:24No data—
Mon 2 NovWaddinxveen Triangel 10:24No data—
Fri 30 OctWaddinxveen Triangel 10:25No data—
Wed 28 OctWaddinxveen Triangel 10:25Partial coverage0 min—
Tue 27 OctWaddinxveen Triangel 10:25Partial coverage0 min—
Mon 26 OctWaddinxveen Triangel 10:27No data—
Fri 23 OctWaddinxveen Triangel 10:24No data—
Thu 22 OctWaddinxveen Triangel 10:26No data—
Wed 21 OctWaddinxveen Triangel 10:26No data—
Tue 20 OctWaddinxveen Triangel 10:24Partial coverage0 min—
Mon 19 OctWaddinxveen Triangel 10:26Partial coverage0 min—
Fri 16 OctWaddinxveen Triangel 10:25No data—
Thu 15 OctWaddinxveen Triangel 10:25No data—
Wed 14 OctWaddinxveen Triangel 10:25No data—
Tue 13 OctWaddinxveen Triangel 10:25No data—
Mon 12 OctWaddinxveen Triangel 10:25No data—
Fri 9 OctWaddinxveen Triangel 10:24Partial coverage0 min—
Thu 8 OctWaddinxveen Triangel 10:24Partial coverage0 min—
Wed 7 OctWaddinxveen Triangel 10:24Partial coverage0 min—
Tue 6 OctWaddinxveen Triangel 10:24Partial coverage0 min—
Mon 5 OctWaddinxveen Triangel 10:24No data—
Fri 2 OctWaddinxveen Triangel 10:25No data—
Thu 1 OctWaddinxveen Triangel 10:24No data—
Wed 30 SeptWaddinxveen Triangel 10:25No data—
Tue 29 SeptWaddinxveen Triangel 10:25No data—
Mon 28 SeptWaddinxveen Triangel 10:24No data—
Fri 25 SeptWaddinxveen Triangel 10:24No data—
Thu 24 SeptWaddinxveen Triangel 10:24No data—