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

Gouda 16:13 → Alphen a/d Rijn 16: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 16:44 No data

  1. Gouda16:13
  2. Waddinxveen Triangel16:19
  3. Waddinxveen16:21
  4. Waddinxveen Noord16:25
  5. Boskoop Snijdelwijk16:27
  6. Boskoop16:29
  7. Alphen a/d Rijn16:35

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

Next departure 16:13 tomorrow · Gouda
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 14 no data
On-time · 90 days
86%
31/36 runs under 3 min
RT coverage: 26 full · 10 partial · 28 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: 0 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

  • Fri 25 Sept Max en route +11 min · last fix heading to Gouda +9 min
  • Tue 22 Sept Max en route +9 min · last fix heading to Gouda +9 min
  • Tue 1 Sept Max en route +8 min · last fix heading to Gouda +6 min
  • Thu 24 Sept Max en route +12 min · last fix heading to Gouda +4 min
  • Tue 15 Sept Max en route +21 min · last fix heading to Gouda +4 min

Distribution · 90 days

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

  • Early 25% · 9
  • On time 61% · 22
  • 3–10 min 14% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 63% T n=8
  • 100% W n=7
  • 83% T n=6
  • 83% F n=6
  • 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, 36 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
16:13on time on time
16:19≈ on time ≈ +1 min
16:21 / 16:23≈ on time ≈ +1 min
16:25≈ on time ≈ +2 min
16:27≈ on time ≈ +3 min
16:29 / 16:30≈ on time ≈ +3 min
16:35on 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
Thu 5 NovBoskoop 16:44No data—
Wed 4 NovBoskoop 16:44Partial coverage0 min—
Tue 3 NovBoskoop 16:44No data—
Mon 2 NovBoskoop 16:44No data—
Fri 30 OctBoskoop 16:45No data—
Thu 29 OctBoskoop 16:44No data—
Wed 28 OctBoskoop 16:46Partial coverage0 min—
Tue 27 OctBoskoop 16:44Partial coverage0 min—
Mon 26 OctBoskoop 16:46No data—
Fri 23 OctBoskoop 16:46No data—
Thu 22 OctBoskoop 16:44No data—
Wed 21 OctBoskoop 16:44No data—
Tue 20 OctBoskoop 16:44Partial coverage0 min—
Mon 19 OctBoskoop 16:44Partial coverage0 min—
Fri 16 OctBoskoop 16:44No data—
Thu 15 OctBoskoop Snijdelwijk 16:53No data—
Wed 14 OctBoskoop 16:44No data—
Tue 13 OctBoskoop 16:45No data—
Mon 12 OctBoskoop 16:44Partial coverage0 min—
Fri 9 OctBoskoop 16:44No data—
Thu 8 OctBoskoop 16:44Partial coverage0 min—
Wed 7 OctBoskoop 16:44Partial coverage0 min—
Tue 6 OctBoskoop 16:44Partial coverage0 min—
Mon 5 OctBoskoop 16:44Partial coverage0 min—
Fri 2 OctGouda 19:540 min+2 min
Thu 1 OctGouda 19:22−1 min+3 min
Wed 30 SeptGouda 17:49+2 min+2 min
Tue 29 SeptGouda 19:21−3 min+2 min
Mon 28 SeptGouda 00:39−1 min—
Fri 25 SeptGouda 01:22+9 min+11 min