Train NS 7323 Breukelen – Rhenen

Breukelen 07:28 → Rhenen 08:21 Daily 0 h 53 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Veenendaal Centrum at 08:33 +3 min

  1. Breukelen07:28
  2. Utrecht Zuilen07:38
  3. Utrecht Centraal07:41
  4. Bunnik07:51
  5. Maarn08:01
  6. Veenendaal Centrum08:13
  7. Rhenen08:21

Next service: tomorrow 07:28 from Breukelen · Thu 12 Nov

Next departure 07:28 tomorrow · Breukelen
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 7 full · 15 partial · 8 no data
On-time · 90 days
98%
53/54 runs under 3 min
RT coverage: 34 full · 20 partial · 35 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: +2 min

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

  • Wed 11 Nov Max en route +5 min · last fix heading to Veenendaal Centrum +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 53
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 100% T n=9
  • 89% W n=9
  • 100% T n=9
  • 100% F n=8
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 54 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
07:28on time on time
07:33≈ on time ≈ on time
07:38≈ on time ≈ on time
07:41 / 07:44≈ on time ≈ on time
07:46≈ on time ≈ on time
07:51≈ on time ≈ on time
07:55≈ on time ≈ on time
08:01≈ on time ≈ on time
08:10≈ on time ≈ on time
08:13 / 08:15≈ on time ≈ on time
08:21on time on time

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 11 NovVeenendaal Centrum 08:33Partial coverage+3 min+5 min
Tue 10 NovVeenendaal Centrum 08:29Partial coverage+2 min+2 min
Mon 9 NovVeenendaal Centrum 08:29Partial coverage+1 min+1 min
Sun 8 NovVeenendaal Centrum 08:290 min—
Sat 7 NovVeenendaal Centrum 08:29Partial coverage0 min—
Fri 6 NovVeenendaal Centrum 08:29No data—
Thu 5 NovVeenendaal Centrum 08:29No data—
Wed 4 NovVeenendaal Centrum 08:29Partial coverage0 min—
Tue 3 NovVeenendaal Centrum 08:34No data—
Mon 2 NovVeenendaal Centrum 08:29Partial coverage0 min—
Sun 1 NovVeenendaal Centrum 08:370 min—
Sat 31 OctVeenendaal Centrum 08:31Partial coverage+3 min+3 min
Fri 30 OctVeenendaal Centrum 08:29Partial coverage0 min—
Thu 29 OctVeenendaal Centrum 08:29Partial coverage0 min—
Wed 28 OctVeenendaal Centrum 08:29Partial coverage0 min—
Tue 27 OctVeenendaal Centrum 08:29Partial coverage0 min—
Mon 26 OctVeenendaal Centrum 08:29Partial coverage0 min—
Sun 25 OctVeenendaal Centrum 08:29No data—
Sat 24 OctVeenendaal Centrum 08:450 min—
Fri 23 OctBunnik 08:030 min—
Thu 22 OctBunnik 08:050 min—
Wed 21 OctBunnik 08:050 min—
Tue 20 OctBunnik 08:05No data—
Mon 19 OctVeenendaal Centrum 08:29Partial coverage0 min—
Sun 18 OctVeenendaal Centrum 08:30+1 min+1 min
Sat 17 OctVeenendaal Centrum 08:30Partial coverage+1 min+2 min
Fri 16 OctVeenendaal Centrum 08:29No data—
Thu 15 OctVeenendaal Centrum 08:29No data—
Wed 14 OctVeenendaal Centrum 08:30No data—
Tue 13 OctVeenendaal Centrum 08:30Partial coverage0 min—