Train R-net NS 8616 Gouda – Alphen a/d Rijn
✓ Today’s run finished
Today, last fix heading to Boskoop at 07:59 +1 min
- Gouda07:28
- Waddinxveen Triangel07:34
- Waddinxveen07:36
- Waddinxveen Noord07:40
- Boskoop Snijdelwijk07:42
- Boskoop07:44
- Alphen a/d Rijn07:50
Next service: tomorrow 07:28 from Gouda · Tue 10 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
- Sat 17 Oct Max en route +5 min · last fix heading to Boskoop +5 min
- Sat 24 Oct Max en route +4 min · last fix heading to Boskoop +4 min
Distribution · 90 days
26 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 12% · 3
- On time 81% · 21
- 3–10 min 8% · 2
- 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=4
- 60% S n=5
- 100% S n=3
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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 07:28 | on time | +1 min | |
| 07:34 | ≈ 1 min early | ≈ on time | |
| 07:36 / 07:38 | ≈ 1 min early | ≈ on time | |
| 07:40 | ≈ 1 min early | ≈ on time | |
| 07:42 | ≈ 2 min early | ≈ on time | |
| 07:44 / 07:45 | ≈ 2 min early | ≈ on time | |
| 07:50 | 3 min early | 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 9 Nov | Boskoop 07:59Partial coverage | +1 min | +1 min |
| Sun 8 Nov | Boskoop 07:59Partial coverage | 0 min | — |
| Sat 7 Nov | Boskoop 08:00Partial coverage | 0 min | — |
| Fri 6 Nov | Boskoop 07:59 | No data | — |
| Thu 5 Nov | Boskoop 08:02 | No data | — |
| Wed 4 Nov | Boskoop 07:59Partial coverage | +2 min | +2 min |
| Tue 3 Nov | Boskoop 08:29 | No data | — |
| Mon 2 Nov | Boskoop 07:59 | No data | — |
| Sun 1 Nov | Boskoop 07:59Partial coverage | 0 min | — |
| Sat 31 Oct | Boskoop 08:00Partial coverage | +1 min | +1 min |
| Fri 30 Oct | Boskoop 08:00Partial coverage | +1 min | +1 min |
| Thu 29 Oct | — 07:37 | No data | — |
| Wed 28 Oct | Boskoop 07:59Partial coverage | 0 min | — |
| Tue 27 Oct | Boskoop 08:00Partial coverage | 0 min | — |
| Mon 26 Oct | Boskoop 08:00Partial coverage | +1 min | +1 min |
| Sun 25 Oct | Boskoop 07:59 | No data | — |
| Sat 24 Oct | Boskoop 08:03Partial coverage | +4 min | +4 min |
| Fri 23 Oct | Boskoop 08:00Partial coverage | +1 min | +1 min |
| Thu 22 Oct | Boskoop 08:00 | No data | — |
| Wed 21 Oct | Boskoop 08:00 | No data | — |
| Tue 20 Oct | Boskoop 07:59Partial coverage | 0 min | — |
| Mon 19 Oct | Boskoop 07:59 | No data | — |
| Sun 18 Oct | Boskoop 07:59Partial coverage | 0 min | — |
| Sat 17 Oct | Boskoop 08:04Partial coverage | +5 min | +5 min |
| Fri 16 Oct | Boskoop 08:00 | No data | — |
| Thu 15 Oct | Boskoop 08:01 | No data | — |
| Wed 14 Oct | Boskoop 08:01 | No data | — |
| Tue 13 Oct | Boskoop 08:01 | No data | — |
| Mon 12 Oct | Boskoop 08:01 | No data | — |
| Sun 11 Oct | Boskoop 07:59 | No data | — |