Train NS 7328 Rhenen – Breukelen

Rhenen 09:38 → Breukelen 10:31 Daily 0 h 53 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

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

Next departure 09:38 today · Rhenen
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 18 full · 3 partial · 8 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 19 full · 3 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 100% W n=4
  • 100% T n=1
  • 100% 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, 22 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
09:38on time on time
09:44 / 09:46≈ on time ≈ on time
09:49≈ on time ≈ on time
09:58≈ on time ≈ +1 min
10:03≈ on time ≈ +1 min
10:08≈ on time ≈ +1 min
10:12≈ on time ≈ +1 min
10:15 / 10:19≈ on time ≈ +1 min
10:22≈ on time ≈ +1 min
10:27≈ on time ≈ +1 min
10:31on 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

DateLast stopFinalMax
Wed 4 NovMaarssen 10:39Partial coverage0 min—
Tue 3 NovMaarssen 10:580 min—
Mon 2 NovMaarssen 10:39No data—
Sun 1 NovMaarssen 10:39+2 min+4 min
Sat 31 OctMaarssen 10:41+1 min—
Fri 30 OctMaarssen 10:410 min—
Thu 29 OctMaarssen 10:41No data—
Wed 28 OctMaarssen 10:44Partial coverage0 min—
Tue 27 OctMaarssen 10:410 min—
Mon 26 OctMaarssen 10:410 min—
Sun 25 OctMaarssen 10:40No data—
Sat 24 OctMaarssen 10:290 min—
Fri 23 OctMaarssen 10:410 min—
Thu 22 OctMaarssen 10:41No data—
Wed 21 OctMaarssen 10:40No data—
Tue 20 OctMaarssen 10:410 min—
Mon 19 OctMaarssen 10:420 min—
Sun 18 OctMaarssen 10:41+1 min+1 min
Sat 17 OctMaarssen 10:410 min—
Fri 16 OctMaarssen 10:41No data—
Thu 15 OctMaarssen 10:44No data—
Wed 14 OctMaarssen 10:42Partial coverage0 min—
Tue 13 OctMaarssen 10:41No data—
Mon 12 OctMaarssen 10:410 min—
Sun 11 OctMaarssen 10:370 min—
Sat 10 OctMaarssen 10:41+1 min+1 min
Fri 9 OctMaarssen 10:41+2 min+2 min
Thu 8 OctMaarssen 10:400 min—
Wed 7 OctMaarssen 12:000 min—
Tue 6 OctMaarssen 10:41+1 min—