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

Alphen a/d Rijn 08:55 → Gouda 09: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 No data

Next service: tomorrow 08:55 from Alphen a/d Rijn · Mon 9 Nov

Next departure 08:55 tomorrow · Alphen a/d Rijn
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 0 full · 4 partial · 15 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 14 full · 8 partial · 41 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

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 1 Oct Max en route +27 min · last fix heading to Alphen a/d Rijn +27 min
  • Mon 5 Oct Max en route +29 min · last fix heading to Alphen a/d Rijn +6 min

Distribution · 90 days

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

  • Early 23% · 5
  • On time 68% · 15
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=4
  • 100% W n=5
  • 75% T n=4
  • 100% F n=4
  • 100% S n=1
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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:55on time on time
08:59 / 09:00≈ on time ≈ +4 min
09:02≈ on time ≈ +7 min
09:04≈ on time ≈ +9 min
09:07≈ on time ≈ +10 min
09:10≈ on time ≈ +7 min
09:17on time +5 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
Fri 6 NovWaddinxveen Triangel 09:24No data—
Thu 5 NovWaddinxveen Triangel 09:27No data—
Wed 4 NovWaddinxveen Triangel 09:24Partial coverage+1 min—
Tue 3 NovWaddinxveen Triangel 09:29No data—
Mon 2 NovWaddinxveen Triangel 09:24No data—
Fri 30 OctWaddinxveen Triangel 09:25No data—
Wed 28 OctWaddinxveen Triangel 09:24Partial coverage0 min—
Tue 27 OctWaddinxveen Triangel 09:25No data—
Mon 26 OctWaddinxveen Triangel 09:25No data—
Fri 23 OctWaddinxveen Triangel 09:25No data—
Thu 22 OctWaddinxveen Triangel 09:25No data—
Wed 21 OctWaddinxveen Triangel 09:25No data—
Tue 20 OctWaddinxveen Triangel 09:24Partial coverage0 min—
Mon 19 OctWaddinxveen Triangel 09:24Partial coverage0 min—
Fri 16 OctWaddinxveen Triangel 09:26No data—
Thu 15 OctWaddinxveen Triangel 09:25No data—
Wed 14 OctWaddinxveen Triangel 09:25No data—
Tue 13 OctWaddinxveen Triangel 09:28No data—
Mon 12 OctWaddinxveen Triangel 09:27No data—
Fri 9 OctWaddinxveen Triangel 09:27Partial coverage+2 min+2 min
Thu 8 OctWaddinxveen Triangel 09:26Partial coverage+2 min+2 min
Wed 7 OctWaddinxveen Triangel 09:24Partial coverage0 min—
Tue 6 OctWaddinxveen Triangel 09:26Partial coverage+3 min+3 min
Mon 5 OctAlphen a/d Rijn 12:20+6 min+29 min
Fri 2 OctAlphen a/d Rijn 17:460 min+33 min
Thu 1 OctAlphen a/d Rijn 01:59+27 min+27 min
Wed 30 SeptAlphen a/d Rijn 20:050 min+10 min
Tue 29 SeptAlphen a/d Rijn 17:36+2 min+6 min
Mon 28 SeptAlphen a/d Rijn 22:59−3 min+4 min
Sat 26 SeptAlphen a/d Rijn 04:01−3 min—