Train NS 7325 Breukelen – Rhenen

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

✓ Today’s run finished

Today, last fix heading to Veenendaal Centrum at 08:59 No data

  1. Breukelen07:58
  2. Utrecht Zuilen08:08
  3. Utrecht Centraal08:11
  4. Bunnik08:21
  5. Maarn08:31
  6. Veenendaal Centrum08:43
  7. Rhenen08:51

Next service: tomorrow 07:58 from Breukelen · Sat 7 Nov

Next departure 07:58 tomorrow · Breukelen
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 7 full · 12 partial · 11 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 7 full · 14 partial · 68 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: 0 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 7 Oct Max en route +7 min · last fix heading to Veenendaal Centrum +6 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

  • — M n=0
  • 100% T n=3
  • 67% W n=3
  • 100% T n=4
  • 100% F n=4
  • 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, 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
07:58on time on time
08:03≈ on time ≈ on time
08:08≈ on time ≈ on time
08:11 / 08:14≈ on time ≈ on time
08:16≈ on time ≈ on time
08:21≈ on time ≈ on time
08:25≈ on time ≈ on time
08:31≈ on time ≈ on time
08:40≈ on time ≈ on time
08:43 / 08:45≈ on time ≈ on time
08:51on 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
Fri 6 NovVeenendaal Centrum 08:59No data—
Thu 5 NovVeenendaal Centrum 08:59Partial coverage0 min—
Wed 4 NovVeenendaal Centrum 08:59Partial coverage0 min—
Tue 3 NovVeenendaal Centrum 08:59No data—
Mon 2 NovVeenendaal Centrum 08:59No data—
Sun 1 NovVeenendaal Centrum 09:070 min—
Sat 31 OctVeenendaal Centrum 08:59Partial coverage0 min—
Fri 30 OctVeenendaal Centrum 08:59Partial coverage0 min—
Thu 29 OctVeenendaal Centrum 09:03Partial coverage0 min—
Wed 28 OctVeenendaal Centrum 08:59No data—
Tue 27 OctVeenendaal Centrum 09:03Partial coverage0 min—
Mon 26 OctVeenendaal Centrum 08:59No data—
Sun 25 OctVeenendaal Centrum 08:59No data—
Sat 24 OctVeenendaal Centrum 09:150 min—
Fri 23 OctBunnik 08:390 min—
Thu 22 OctBunnik 08:340 min—
Wed 21 OctBunnik 08:350 min—
Tue 20 OctBunnik 08:350 min—
Mon 19 OctVeenendaal Centrum 08:59No data—
Sun 18 OctVeenendaal Centrum 09:00Partial coverage+1 min—
Sat 17 OctVeenendaal Centrum 08:59Partial coverage0 min—
Fri 16 OctVeenendaal Centrum 08:59Partial coverage0 min—
Thu 15 OctVeenendaal Centrum 08:59No data—
Wed 14 OctVeenendaal Centrum 08:59No data—
Tue 13 OctVeenendaal Centrum 08:59No data—
Mon 12 OctVeenendaal Centrum 08:59No data—
Sun 11 OctVeenendaal Centrum 09:010 min—
Sat 10 OctVeenendaal Centrum 09:01Partial coverage+2 min+2 min
Fri 9 OctVeenendaal Centrum 08:59Partial coverage0 min—
Thu 8 OctVeenendaal Centrum 08:59Partial coverage0 min+1 min