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

Alphen a/d Rijn 18:40 → Gouda 19:02 Daily 0 h 22 min · 7 stops R-net NS

✓ Today’s run finished

Today, last fix heading to Waddinxveen Triangel at 19:09 +2 min

  1. Alphen a/d Rijn18:40
  2. Boskoop18:44
  3. Boskoop Snijdelwijk18:47
  4. Waddinxveen Noord18:49
  5. Waddinxveen18:52
  6. Waddinxveen Triangel18:55
  7. Gouda19:02

Next service: tomorrow 18:40 from Alphen a/d Rijn · Sun 8 Nov

Next departure 18:40 tomorrow · Alphen a/d Rijn
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 6 full · 10 partial · 13 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 10 full · 10 partial · 47 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 Gouda, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 29 Oct Max en route +15 min · last fix heading to — +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
18:40on time on time
18:44 / 18:45≈ on time ≈ +2 min
18:47≈ on time ≈ +2 min
18:49≈ on time ≈ +2 min
18:52≈ on time ≈ +2 min
18:55≈ on time ≈ +2 min
19:02on time +2 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
Sat 7 NovWaddinxveen Triangel 19:09Partial coverage+2 min+2 min
Fri 6 NovBoskoop Snijdelwijk 19:03Partial coverage0 min—
Thu 5 Nov— 19:03No data—
Wed 4 Nov— 19:040 min—
Mon 2 Nov— 19:03+1 min—
Sun 1 NovWaddinxveen Triangel 19:09Partial coverage0 min—
Sat 31 OctWaddinxveen Triangel 19:11Partial coverage0 min+1 min
Fri 30 OctWaddinxveen 19:06No data—
Thu 29 Oct— 18:56+15 min+15 min
Wed 28 Oct— 19:070 min—
Tue 27 Oct— 19:060 min—
Mon 26 Oct— 19:03No data—
Sun 25 OctWaddinxveen Triangel 19:09No data—
Sat 24 OctWaddinxveen Triangel 19:11No data—
Fri 23 OctWaddinxveen Triangel 19:09Partial coverage+1 min+2 min
Thu 22 OctBoskoop 19:14No data—
Wed 21 OctAlphen a/d Rijn 19:04No data—
Tue 20 OctBoskoop 19:04Partial coverage0 min—
Mon 19 OctAlphen a/d Rijn 19:04No data—
Sun 18 OctWaddinxveen Triangel 19:09Partial coverage+1 min+1 min
Sat 17 OctWaddinxveen Triangel 19:10No data—
Fri 16 OctWaddinxveen Triangel 19:09No data—
Thu 15 Oct— 19:05No data—
Wed 14 OctWaddinxveen Triangel 19:09No data—
Tue 13 OctAlphen a/d Rijn 18:50No data—
Mon 12 OctBoskoop 19:04Partial coverage0 min—
Sun 11 OctWaddinxveen Triangel 19:10Partial coverage0 min—
Sat 10 OctWaddinxveen Triangel 19:09Partial coverage0 min—
Fri 9 Oct— 19:030 min—
Thu 8 Oct— 19:040 min—