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