Train NS 7362 Rhenen – Breukelen
It has not run yet today
Last recorded run: Tuesday 10 November +16 min
Next service: today 18:08 from Rhenen · Wed 11 Nov
Last 30 days
Arrival delay at Breukelen, 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 10 Nov Max en route +16 min · last fix heading to Veenendaal West +16 min
- Sat 7 Nov Max en route +15 min · last fix heading to Maarssen +15 min
Distribution · 90 days
29 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 27
- 3–10 min 0% · 0
- 10–30 min 7% · 2
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 75% T n=4
- 100% W n=5
- 100% T n=4
- 100% F n=3
- 75% S n=4
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 29 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 |
|---|---|---|---|
| 18:08 | on time | on time | |
| 18:14 / 18:16 | ≈ on time | ≈ on time | |
| 18:19 | ≈ on time | ≈ on time | |
| 18:28 | ≈ on time | ≈ +1 min | |
| 18:34 | ≈ on time | ≈ +1 min | |
| 18:38 | ≈ on time | ≈ +1 min | |
| 18:43 | ≈ on time | ≈ +1 min | |
| 18:46 / 18:49 | ≈ on time | ≈ +1 min | |
| 18:52 | ≈ on time | ≈ +1 min | |
| 18:56 | ≈ on time | ≈ +1 min | |
| 19:00 | on time | +1 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 |
|---|---|---|---|
| Tue 10 Nov | Veenendaal West 19:24Partial coverage | +16 min | +16 min |
| Mon 9 Nov | Rhenen 19:04Partial coverage | +1 min | +1 min |
| Sun 8 Nov | Maarssen 19:09Partial coverage | 0 min | — |
| Sat 7 Nov | Maarssen 19:24Partial coverage | +15 min | +15 min |
| Fri 6 Nov | Utrecht Vaartsche Rijn 19:04Partial coverage | +3 min | +3 min |
| Thu 5 Nov | Rhenen 18:59Partial coverage | 0 min | — |
| Wed 4 Nov | Rhenen 19:02 | 0 min | — |
| Tue 3 Nov | Rhenen 19:05Partial coverage | 0 min | — |
| Mon 2 Nov | Rhenen 18:59Partial coverage | +1 min | +1 min |
| Sun 1 Nov | Maarssen 19:09 | 0 min | — |
| Sat 31 Oct | Maarssen 19:11Partial coverage | +1 min | +1 min |
| Fri 30 Oct | Utrecht Zuilen 19:06 | No data | — |
| Wed 28 Oct | Rhenen 19:25 | 0 min | — |
| Tue 27 Oct | — 19:07 | 0 min | — |
| Mon 26 Oct | Rhenen 19:13Partial coverage | 0 min | — |
| Sun 25 Oct | Maarssen 19:11 | No data | — |
| Sat 24 Oct | Krommenie-Assendelft 20:07 | 0 min | — |
| Fri 23 Oct | Maarssen 19:10 | +1 min | — |
| Thu 22 Oct | Utrecht Vaartsche Rijn 19:04 | 0 min | — |
| Wed 21 Oct | Bunnik 19:02 | 0 min | — |
| Tue 20 Oct | Utrecht Vaartsche Rijn 19:11 | No data | — |
| Mon 19 Oct | Utrecht Vaartsche Rijn 19:02 | No data | — |
| Sun 18 Oct | Maarssen 19:11Partial coverage | +1 min | +1 min |
| Sat 17 Oct | Maarssen 19:11 | No data | — |
| Fri 16 Oct | Maarssen 19:10 | No data | — |
| Thu 15 Oct | Maarn 19:04Partial coverage | 0 min | — |
| Wed 14 Oct | Maarssen 19:09 | 0 min | — |
| Tue 13 Oct | Bunnik 19:04 | No data | — |
| Mon 12 Oct | Utrecht Vaartsche Rijn 19:02 | 0 min | — |
| Sun 11 Oct | Maarssen 19:09 | +3 min | +3 min |