Train R-net NS 8712 Gouda – Alphen a/d Rijn
✓ Today’s run finished
Today, last fix heading to Boskoop at 07:14 No data
- Gouda06:43
- Waddinxveen Triangel06:49
- Waddinxveen06:51
- Waddinxveen Noord06:55
- Boskoop Snijdelwijk06:57
- Boskoop06:59
- Alphen a/d Rijn07:05
Next service: tomorrow 06:43 from Gouda · Fri 6 Nov
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
- Tue 27 Oct Max en route +15 min · last fix heading to Boskoop +15 min
- Mon 12 Oct Max en route +4 min · last fix heading to Boskoop +4 min
- Fri 30 Oct Max en route +3 min · last fix heading to Boskoop +3 min
- Wed 14 Oct Max en route +3 min · last fix heading to Boskoop +3 min
- Wed 4 Nov Max en route +3 min · last fix heading to Boskoop +3 min
Distribution · 90 days
21 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 76% · 16
- 3–10 min 19% · 4
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 80% T n=5
- 60% W n=5
- 100% T n=4
- 75% F n=4
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 21 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 06:43 | on time | +1 min | |
| 06:49 | — | — | |
| 06:51 / 06:53 | — | — | |
| 06:55 | — | — | |
| 06:57 | — | — | |
| 06:59 / 07:00 | — | — | |
| 07:05 | — | — |
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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 5 Nov | Boskoop 07:14 | No data | — |
| Wed 4 Nov | Boskoop 07:17Partial coverage | +3 min | +3 min |
| Tue 3 Nov | Boskoop 07:14Partial coverage | +1 min | +1 min |
| Mon 2 Nov | Boskoop 07:14 | No data | — |
| Fri 30 Oct | Boskoop 07:18Partial coverage | +3 min | +3 min |
| Thu 29 Oct | Boskoop 07:14Partial coverage | 0 min | — |
| Wed 28 Oct | Boskoop 07:14Partial coverage | 0 min | — |
| Tue 27 Oct | Boskoop 07:29Partial coverage | +15 min | +15 min |
| Mon 26 Oct | Boskoop 07:15Partial coverage | +1 min | +1 min |
| Fri 23 Oct | Boskoop 07:15Partial coverage | 0 min | — |
| Thu 22 Oct | Boskoop 07:16Partial coverage | +2 min | +2 min |
| Wed 21 Oct | Boskoop 07:15Partial coverage | 0 min | — |
| Tue 20 Oct | Boskoop 07:15Partial coverage | +1 min | +2 min |
| Mon 19 Oct | Boskoop 07:16Partial coverage | +2 min | +2 min |
| Fri 16 Oct | Boskoop 07:15Partial coverage | +1 min | +2 min |
| Thu 15 Oct | Boskoop 07:16Partial coverage | +2 min | +2 min |
| Wed 14 Oct | Boskoop 07:17Partial coverage | +3 min | +3 min |
| Tue 13 Oct | Boskoop 07:15Partial coverage | +3 min | +3 min |
| Mon 12 Oct | Boskoop 07:17Partial coverage | +4 min | +4 min |
| Fri 9 Oct | Boskoop 07:15Partial coverage | +1 min | +1 min |
| Thu 8 Oct | Boskoop 07:15Partial coverage | +1 min | +1 min |
| Wed 7 Oct | Boskoop 07:14Partial coverage | 0 min | — |
| Tue 6 Oct | Boskoop 07:15Partial coverage | +1 min | — |
| Mon 5 Oct | Boskoop 07:15 | No data | — |
| Fri 2 Oct | Boskoop 07:16 | No data | — |
| Thu 1 Oct | Boskoop 07:14 | No data | — |
| Wed 30 Sept | Boskoop 07:14 | No data | — |
| Tue 29 Sept | Boskoop 07:15 | No data | — |
| Mon 28 Sept | Boskoop 07:14 | No data | — |
| Fri 25 Sept | Boskoop 07:14 | No data | — |