Train R-net NS 8743 Alphen a/d Rijn – Gouda
✓ Today’s run finished
Today, last fix heading to Waddinxveen Triangel at 14:54 No data
- Alphen a/d Rijn14:25
- Boskoop14:29
- Boskoop Snijdelwijk14:32
- Waddinxveen Noord14:34
- Waddinxveen14:37
- Waddinxveen Triangel14:40
- Gouda14:47
Next service: tomorrow 14:25 from Alphen a/d Rijn · Fri 6 Nov
Last 30 days
Arrival delay at Gouda, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 23 Sept Max en route +8 min · last fix heading to Alphen a/d Rijn +8 min
- Tue 15 Sept Max en route +8 min · last fix heading to Waddinxveen Triangel +5 min
Distribution · 90 days
24 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 21% · 5
- On time 71% · 17
- 3–10 min 8% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 80% T n=5
- 83% W n=6
- 100% T n=4
- 100% 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, 24 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 |
|---|---|---|---|
| 14:25 | on time | on time | |
| 14:29 / 14:30 | ≈ on time | ≈ +1 min | |
| 14:32 | ≈ on time | ≈ +1 min | |
| 14:34 | ≈ on time | ≈ +2 min | |
| 14:37 | ≈ on time | ≈ +2 min | |
| 14:40 | ≈ on time | ≈ +3 min | |
| 14:47 | on time | +4 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 5 Nov | Waddinxveen Triangel 14:54 | No data | — |
| Wed 4 Nov | Waddinxveen Triangel 14:54Partial coverage | 0 min | — |
| Tue 3 Nov | Waddinxveen Triangel 14:54 | No data | — |
| Mon 2 Nov | Waddinxveen Triangel 14:54 | No data | — |
| Fri 30 Oct | Waddinxveen Triangel 14:54 | No data | — |
| Thu 29 Oct | — 14:37 | No data | — |
| Wed 28 Oct | Waddinxveen Triangel 14:56Partial coverage | 0 min | — |
| Tue 27 Oct | Waddinxveen Triangel 14:56Partial coverage | 0 min | — |
| Mon 26 Oct | Waddinxveen Triangel 14:55 | No data | — |
| Fri 23 Oct | Waddinxveen Triangel 15:00 | No data | — |
| Thu 22 Oct | Waddinxveen Triangel 14:54 | No data | — |
| Wed 21 Oct | Waddinxveen Triangel 14:54 | No data | — |
| Tue 20 Oct | Waddinxveen Triangel 14:55Partial coverage | 0 min | — |
| Mon 19 Oct | Waddinxveen Triangel 14:54Partial coverage | 0 min | — |
| Fri 16 Oct | Waddinxveen Triangel 14:55 | No data | — |
| Thu 15 Oct | Waddinxveen Triangel 14:54 | No data | — |
| Wed 14 Oct | Waddinxveen Triangel 14:55 | No data | — |
| Tue 13 Oct | Waddinxveen Triangel 14:56 | No data | — |
| Mon 12 Oct | Waddinxveen Triangel 14:55 | No data | — |
| Fri 9 Oct | Waddinxveen Triangel 14:54Partial coverage | 0 min | — |
| Thu 8 Oct | Waddinxveen Triangel 14:54Partial coverage | 0 min | — |
| Wed 7 Oct | Waddinxveen Triangel 14:55Partial coverage | +1 min | +1 min |
| Tue 6 Oct | Waddinxveen Triangel 14:55Partial coverage | +1 min | — |
| Mon 5 Oct | Waddinxveen Triangel 14:54Partial coverage | 0 min | — |
| Fri 2 Oct | Alphen a/d Rijn 18:55 | −1 min | +4 min |
| Thu 1 Oct | Alphen a/d Rijn 19:03 | −2 min | +1 min |
| Wed 30 Sept | Alphen a/d Rijn 01:33 | 0 min | +3 min |
| Tue 29 Sept | Alphen a/d Rijn 17:56 | −1 min | +2 min |
| Mon 28 Sept | Alphen a/d Rijn 01:31 | 0 min | +3 min |
| Fri 25 Sept | Alphen a/d Rijn 23:32 | 0 min | +7 min |