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

Gouda 08:58 → Alphen a/d Rijn 09:20 Daily 0 h 22 min · 7 stops R-net NS

✓ Today’s run finished

Today, last fix heading to Boskoop at 09:29 0 min

  1. Gouda08:58
  2. Waddinxveen Triangel09:04
  3. Waddinxveen09:06
  4. Waddinxveen Noord09:10
  5. Boskoop Snijdelwijk09:12
  6. Boskoop09:14
  7. Alphen a/d Rijn09:20

Next service: tomorrow 08:58 from Gouda · Tue 10 Nov

Next departure 08:58 tomorrow · Gouda
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 16 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 8 full · 18 partial · 62 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

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

  • Early 27% · 7
  • On time 73% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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:58on time on time
09:04≈ 1 min early ≈ on time
09:06 / 09:08≈ 1 min early ≈ on time
09:10≈ 2 min early ≈ 1 min early
09:12≈ 3 min early ≈ 1 min early
09:14 / 09:15≈ 3 min early ≈ 1 min early
09:204 min early 1 min early

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