Train NS 7376 Rhenen – Breukelen

Rhenen 21:38 → Breukelen 22:30 Daily 0 h 52 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

Next service: today 21:38 from Rhenen · Thu 5 Nov

Next departure 21:38 today · Rhenen
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 13 full · 4 partial · 11 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 15 full · 4 partial · 29 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

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

  • Fri 23 Oct Max en route +8 min · last fix heading to — +8 min
  • Mon 12 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

19 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 67% F n=3
  • 100% S n=4
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 stops).

Last 90 days, 19 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.

StopSched.Usually 9 days in 10
21:38on time on time
21:44 / 21:46≈ on time ≈ on time
21:49≈ on time ≈ +1 min
21:58≈ on time ≈ +2 min
22:04≈ on time ≈ +2 min
22:08≈ +1 min ≈ +2 min
22:13≈ +1 min ≈ +3 min
22:16 / 22:19≈ +1 min ≈ +3 min
22:22≈ +1 min ≈ +3 min
22:26≈ +1 min ≈ +4 min
22:30+1 min +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

DateLast stopFinalMax
Wed 4 Nov— 22:34+2 min+2 min
Tue 3 Nov— 22:32No data—
Mon 2 Nov— 22:290 min—
Sun 1 NovMaarssen 22:380 min—
Sat 31 OctMaarssen 22:40Partial coverage0 min—
Fri 30 Oct— 22:31No data—
Thu 29 Oct— 22:31+1 min+1 min
Wed 28 Oct— 22:31No data—
Tue 27 Oct— 22:320 min—
Mon 26 Oct— 22:31No data—
Sun 25 OctMaarssen 22:41No data—
Sat 24 OctDuivendrecht 23:300 min—
Fri 23 Oct— 22:48+8 min+8 min
Thu 22 Oct— 22:31No data—
Wed 21 Oct— 22:34No data—
Tue 20 Oct— 22:25No data—
Sun 18 OctMaarssen 22:41Partial coverage+1 min—
Sat 17 OctMaarssen 22:41Partial coverage0 min—
Fri 16 Oct— 22:32+1 min+1 min
Thu 15 Oct— 22:38No data—
Wed 14 Oct— 22:35No data—
Tue 13 Oct— 22:34No data—
Mon 12 Oct— 22:42+6 min+6 min
Sun 11 OctMaarssen 22:370 min—
Sat 10 OctDriebergen-Zeist 22:32Partial coverage+1 min+1 min
Fri 9 Oct— 22:32+1 min+1 min
Thu 8 Oct— 22:32+1 min—
Wed 7 Oct— 22:33+1 min+1 min
Tue 6 Oct— 22:310 min—
Mon 5 Oct— 22:310 min—