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

Gouda 10:21 → Alphen a/d Rijn 10:50 Daily 0 h 29 min · 7 stops R-net NS

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 10:21 from Gouda · Tue 10 Nov

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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
10:21on time on time
10:26— —
10:29 / 10:37— —
10:40— —
10:42— —
10:44 / 10:45— —
10:50— —

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 10:59Partial coverage0 min—
Sun 8 NovBoskoop 10:59Partial coverage0 min—
Sat 7 NovBoskoop 10:59Partial coverage0 min—
Fri 6 NovBoskoop 10:59No data—
Thu 5 NovBoskoop 10:59No data—
Wed 4 NovBoskoop 10:59Partial coverage0 min—
Tue 3 NovBoskoop 11:19No data—
Mon 2 NovBoskoop 10:59No data—
Sun 1 NovBoskoop 11:01Partial coverage+1 min+1 min
Sat 31 OctBoskoop 11:00Partial coverage+1 min+1 min
Fri 30 OctBoskoop 10:59No data—
Thu 29 Oct— 10:37No data—
Wed 28 OctBoskoop 10:59Partial coverage0 min—
Tue 27 OctBoskoop 10:59Partial coverage0 min—
Mon 26 OctBoskoop 11:00No data—
Sun 25 OctBoskoop 10:59No data—
Sat 24 OctBoskoop 10:59Partial coverage0 min—
Fri 23 OctBoskoop 10:59No data—
Thu 22 OctBoskoop 11:00No data—
Wed 21 OctBoskoop 10:59No data—
Tue 20 OctBoskoop 10:59Partial coverage0 min—
Mon 19 OctBoskoop 10:59No data—
Sun 18 OctBoskoop 10:59Partial coverage0 min—
Sat 17 OctBoskoop 10:59No data—
Fri 16 OctBoskoop 10:59No data—
Thu 15 OctBoskoop 10:59No data—
Wed 14 OctBoskoop 10:59No data—
Tue 13 OctBoskoop 10:59No data—
Mon 12 OctBoskoop 10:59No data—
Sun 11 OctBoskoop 10:59Partial coverage0 min—