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

Gouda 14:13 → Alphen a/d Rijn 14:35 Mon, Tue, Wed, Thu, Fri 0 h 22 min · 7 stops R-net NS

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 14:13 from Gouda · Thu 5 Nov

Next departure 14:13 today · Gouda
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 0 full · 6 partial · 15 no data
On-time · 90 days
87%
40/46 runs under 3 min
RT coverage: 39 full · 7 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
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 +18 min · last fix heading to Gouda +18 min
  • Thu 3 Sept Max en route +18 min · last fix heading to Gouda +9 min
  • Thu 17 Sept Max en route +10 min · last fix heading to Gouda +6 min
  • Wed 2 Sept Max en route +6 min · last fix heading to Gouda +5 min
  • Thu 24 Sept Max en route +5 min · last fix heading to Gouda +5 min

Distribution · 90 days

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

  • Early 37% · 17
  • On time 50% · 23
  • 3–10 min 11% · 5
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 100% T n=10
  • 89% W n=9
  • 50% T n=8
  • 89% F n=9
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 46 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
14:13on time on time
14:19≈ on time ≈ +1 min
14:21 / 14:23≈ on time ≈ +2 min
14:25≈ on time ≈ +3 min
14:27≈ on time ≈ +3 min
14:29 / 14:30≈ on time ≈ +3 min
14:351 min early +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
Wed 4 NovBoskoop 14:44Partial coverage0 min—
Tue 3 NovBoskoop 14:44No data—
Mon 2 NovBoskoop 14:44No data—
Fri 30 OctBoskoop 14:44No data—
Thu 29 OctBoskoop 14:45No data—
Wed 28 OctBoskoop 14:44Partial coverage0 min—
Tue 27 OctBoskoop 14:44Partial coverage0 min—
Mon 26 OctBoskoop 14:44No data—
Fri 23 OctBoskoop 14:49No data—
Thu 22 OctBoskoop 14:44No data—
Wed 21 OctBoskoop 14:44No data—
Tue 20 OctBoskoop 14:44Partial coverage0 min—
Mon 19 OctBoskoop 14:45Partial coverage0 min—
Fri 16 OctBoskoop 14:45No data—
Thu 15 OctGouda 14:36No data—
Wed 14 OctBoskoop 14:45No data—
Tue 13 OctBoskoop 14:45No data—
Mon 12 OctBoskoop 14:44No data—
Fri 9 OctBoskoop 14:44Partial coverage0 min—
Thu 8 OctBoskoop 14:44No data—
Wed 7 OctBoskoop 14:44No data—
Tue 6 OctBoskoop 14:44No data—
Mon 5 OctBoskoop 14:44Partial coverage0 min—
Fri 2 OctGouda 17:45−4 min+2 min
Thu 1 OctGouda 17:50+1 min+4 min
Wed 30 SeptGouda 00:41−2 min+52 min
Tue 29 SeptGouda 19:51−1 min+8 min
Mon 28 SeptGouda 01:08−4 min+49 min
Fri 25 SeptGouda 19:25+18 min+18 min
Thu 24 SeptGouda 18:11+5 min+5 min