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

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

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: Monday 17:55 from Alphen a/d Rijn · Mon 9 Nov

Next departure 17:55 Monday · Alphen a/d Rijn
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 11 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 50 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

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

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

On-time by weekday

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

Stops and timetable

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

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