Train NS 7332 Rhenen – Breukelen

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

It has not run yet today

Last recorded run: Saturday 7 November +2 min

Next service: today 10:38 from Rhenen · Sun 8 Nov

Next departure 10:38 today · Rhenen
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 9 full · 8 partial · 12 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 9 full · 12 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sun 18 Oct Max en route +7 min · last fix heading to Krommenie-Assendelft +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
10:38on time on time
10:44 / 10:46≈ on time ≈ on time
10:49≈ on time ≈ +1 min
10:58≈ on time ≈ +1 min
11:04≈ on time ≈ +2 min
11:08≈ on time ≈ +2 min
11:13≈ on time ≈ +3 min
11:16 / 11:19≈ on time ≈ +3 min
11:22≈ on time ≈ +3 min
11:26≈ on time ≈ +3 min
11:30on 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

DateLast stopFinalMax
Sat 7 NovMaarssen 11:42Partial coverage+2 min+2 min
Fri 6 NovMaarssen 11:39No data—
Thu 5 NovMaarssen 11:39No data—
Wed 4 NovMaarssen 11:39Partial coverage+2 min+2 min
Tue 3 NovMaarssen 11:40No data—
Mon 2 NovMaarssen 11:39Partial coverage0 min—
Sun 1 NovMaarssen 11:370 min—
Sat 31 OctKrommenie-Assendelft 12:40+3 min+5 min
Fri 30 OctMaarssen 11:40Partial coverage0 min—
Thu 29 OctMaarssen 11:41No data—
Wed 28 OctDriebergen-Zeist 12:25Partial coverage0 min—
Tue 27 OctMaarssen 11:41No data—
Mon 26 OctMaarssen 11:41Partial coverage0 min—
Sun 25 OctKrommenie-Assendelft 12:37No data—
Sat 24 OctKrommenie-Assendelft 12:37+1 min+1 min
Fri 23 OctMaarssen 11:410 min—
Thu 22 OctMaarssen 11:410 min—
Wed 21 OctMaarssen 11:410 min—
Tue 20 OctMaarssen 11:41No data—
Mon 19 OctMaarssen 11:41Partial coverage0 min—
Sun 18 OctKrommenie-Assendelft 12:44+7 min+7 min
Sat 17 OctZaandijk Zaanse Schans 12:35No data—
Fri 16 OctMaarssen 11:41No data—
Thu 15 OctMaarssen 11:46No data—
Wed 14 OctMaarssen 11:41No data—
Tue 13 OctMaarssen 11:41No data—
Mon 12 OctMaarssen 11:41Partial coverage0 min—
Sun 11 OctMaarssen 11:370 min—
Sat 10 OctKrommenie-Assendelft 12:38+1 min+1 min
Fri 9 OctMaarssen 11:41Partial coverage+1 min—