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

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 13:43 from Gouda · Mon 9 Nov

Next departure 13:43 today · Gouda
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 15 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 5 full · 8 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Distribution · 90 days

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

  • Early 15% · 2
  • On time 85% · 11
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
13:43on time on time
13:49≈ 1 min early ≈ on time
13:51 / 13:53≈ 1 min early ≈ on time
13:55≈ 2 min early ≈ on time
13:57≈ 1 min early ≈ on time
13:59 / 14:00≈ 1 min early ≈ on time
14:05on time on time

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 NovBoskoop 14:14No data—
Thu 5 NovBoskoop 14:14No data—
Wed 4 NovBoskoop 14:14Partial coverage0 min—
Tue 3 NovBoskoop 14:14No data—
Mon 2 NovBoskoop 14:14No data—
Fri 30 OctBoskoop 14:14No data—
Thu 29 OctBoskoop 14:14Partial coverage0 min—
Wed 28 OctBoskoop 14:14Partial coverage0 min—
Tue 27 OctBoskoop 14:14No data—
Mon 26 OctBoskoop 14:16No data—
Fri 23 OctBoskoop 14:15No data—
Thu 22 OctBoskoop 14:14No data—
Wed 21 OctBoskoop 14:14No data—
Tue 20 OctBoskoop 14:14Partial coverage0 min—
Mon 19 OctBoskoop 14:14Partial coverage0 min—
Fri 16 OctBoskoop 14:15No data—
Thu 15 OctBoskoop 14:16No data—
Wed 14 OctBoskoop 14:14No data—
Tue 13 OctBoskoop 14:14No data—
Mon 12 OctBoskoop 14:14No data—
Fri 9 OctBoskoop 14:14Partial coverage0 min—
Thu 8 OctBoskoop 14:14No data—
Wed 7 OctBoskoop 14:14Partial coverage0 min—
Tue 6 OctBoskoop 14:14No data—
Mon 5 OctBoskoop 14:14Partial coverage0 min—
Fri 2 OctBoskoop 14:14No data—
Thu 1 OctBoskoop 14:14No data—
Wed 30 SeptBoskoop 14:15No data—
Tue 29 SeptBoskoop 14:14No data—
Mon 28 SeptBoskoop 14:19No data—