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

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

✓ Today’s run finished

Today, last fix heading to Boskoop at 07:44 No data

  1. Gouda07:13
  2. Waddinxveen Triangel07:19
  3. Waddinxveen07:21
  4. Waddinxveen Noord07:25
  5. Boskoop Snijdelwijk07:27
  6. Boskoop07:29
  7. Alphen a/d Rijn07:35

Next service: tomorrow 07:13 from Gouda · Fri 6 Nov

Next departure 07:13 tomorrow · Gouda
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 0 full · 14 partial · 8 no data
On-time · 90 days
86%
37/43 runs under 3 min
RT coverage: 28 full · 15 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Tue 22 Sept Max en route +34 min · last fix heading to Gouda +20 min
  • Fri 25 Sept Max en route +15 min · last fix heading to Gouda +14 min
  • Wed 16 Sept Max en route +8 min · last fix heading to Gouda +8 min
  • Thu 10 Sept Max en route +40 min · last fix heading to Gouda +5 min
  • Tue 27 Oct Max en route +4 min · last fix heading to Boskoop +4 min

Distribution · 90 days

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

  • Early 23% · 10
  • On time 63% · 27
  • 3–10 min 9% · 4
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 78% T n=9
  • 88% W n=8
  • 89% T n=9
  • 89% F n=9
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 43 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
07:13on time on time
07:19≈ on time ≈ +2 min
07:21 / 07:23≈ on time ≈ +2 min
07:25≈ on time ≈ +3 min
07:27≈ on time ≈ +4 min
07:29 / 07:30≈ on time ≈ +4 min
07:35on time +6 min

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 NovBoskoop 07:44No data—
Wed 4 NovBoskoop 07:44Partial coverage+1 min+2 min
Tue 3 NovBoskoop 07:44Partial coverage0 min—
Mon 2 NovBoskoop 07:44No data—
Fri 30 OctBoskoop 07:47Partial coverage+3 min+3 min
Thu 29 OctBoskoop 07:44Partial coverage0 min—
Wed 28 OctBoskoop 07:44Partial coverage0 min—
Tue 27 OctBoskoop 07:45Partial coverage+4 min+4 min
Mon 26 OctBoskoop 07:45Partial coverage+1 min+1 min
Fri 23 OctBoskoop 07:45Partial coverage+1 min+1 min
Thu 22 OctBoskoop 07:46No data—
Wed 21 OctBoskoop 07:44Partial coverage0 min—
Tue 20 OctBoskoop 07:45Partial coverage0 min—
Mon 19 OctBoskoop 07:45Partial coverage0 min—
Fri 16 OctBoskoop 07:45No data—
Thu 15 OctBoskoop 07:45Partial coverage0 min—
Wed 14 OctBoskoop 07:48No data—
Tue 13 OctBoskoop 07:44Partial coverageNo data—
Mon 12 OctBoskoop 07:47No data—
Fri 9 OctBoskoop 07:44Partial coverage0 min—
Thu 8 OctBoskoop 07:46Partial coverage+2 min+2 min
Wed 7 OctBoskoop 07:44No data—
Tue 6 OctBoskoop 07:44Partial coverage0 min—
Mon 5 OctGouda 11:22−2 min+2 min
Fri 2 OctGouda 19:22−2 min+7 min
Thu 1 OctGouda 18:08+1 min+6 min
Wed 30 SeptGouda 19:55+1 min+6 min
Tue 29 SeptGouda 19:090 min+5 min
Mon 28 SeptGouda 19:530 min+10 min
Fri 25 SeptGouda 00:56+14 min+15 min