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

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

It has not run yet today

Last recorded run: Monday 9 November +1 min

Next service: today 08:13 from Gouda · Tue 10 Nov

Next departure 08:13 today · Gouda
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 0 full · 7 partial · 14 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 2 full · 11 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Tue 6 Oct Max en route +4 min · last fix heading to Boskoop +3 min

Distribution · 90 days

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

  • Early 8% · 1
  • On time 85% · 11
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 75% T n=4
  • 100% W n=4
  • 100% T n=2
  • 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, 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
08:13on time on time
08:19— —
08:21 / 08:23— —
08:25— —
08:27— —
08:29 / 08:30— —
08:35— —

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 08:44Partial coverage+1 min+2 min
Fri 6 NovBoskoop 08:44No data—
Thu 5 NovBoskoop 08:47No data—
Wed 4 NovBoskoop 08:44Partial coverage+3 min+3 min
Tue 3 NovGouda 08:54No data—
Mon 2 NovBoskoop 08:44No data—
Fri 30 OctBoskoop 08:45No data—
Thu 29 OctBoskoop 08:47Partial coverage0 min—
Wed 28 OctBoskoop 08:44Partial coverage0 min—
Tue 27 OctBoskoop 08:47Partial coverage0 min—
Mon 26 OctBoskoop 08:45No data—
Fri 23 OctBoskoop 08:44No data—
Thu 22 OctBoskoop 08:47No data—
Wed 21 OctBoskoop 08:45No data—
Tue 20 OctBoskoop 08:44Partial coverage0 min—
Mon 19 OctBoskoop 08:45Partial coverage0 min—
Fri 16 OctBoskoop 08:44No data—
Thu 15 OctBoskoop 08:45No data—
Wed 14 OctBoskoop 08:44No data—
Tue 13 OctBoskoop 08:44No data—
Mon 12 OctBoskoop 08:46No data—
Fri 9 OctBoskoop 08:44Partial coverage0 min—
Thu 8 OctBoskoop 08:44Partial coverage0 min—
Wed 7 OctBoskoop 08:44Partial coverage0 min—
Tue 6 OctBoskoop 08:48Partial coverage+3 min+4 min
Mon 5 OctBoskoop 08:47No data—
Fri 2 OctBoskoop 08:44No data—
Thu 1 OctBoskoop 08:44No data—
Wed 30 SeptBoskoop 08:44No data—
Tue 29 SeptBoskoop 08:45No data—