Train NS 7327 Breukelen – Rhenen

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

Running now · updated 09:28

Heading to Rhenen 0 min

Estimated arrival at Rhenen 09:21

  1. Breukelen08:28
  2. Utrecht Zuilen08:38
  3. Utrecht Centraal08:41
  4. Bunnik08:51
  5. Maarn09:01
  6. Veenendaal West09:10
  7. Rhenen09:21

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 18 runs arrived on time.

On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 9 full · 9 partial · 12 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 9 full · 10 partial · 70 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 Rhenen, 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 100% F n=2
  • 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 10Today
08:28on time on time
08:33≈ on time ≈ on time
08:38≈ on time ≈ on time
08:41 / 08:44≈ on time ≈ on time
08:46≈ on time ≈ on time
08:51≈ on time ≈ on time
08:55≈ on time ≈ +1 min
09:01≈ on time ≈ +1 min
09:10≈ on time ≈ +1 min
09:13 / 09:15≈ on time ≈ +1 min
09:21on 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
Thu 5 NovVeenendaal Centrum 09:24Partial coverage0 min—
Wed 4 NovVeenendaal Centrum 09:29Partial coverage0 min+1 min
Tue 3 NovVeenendaal Centrum 09:29No data—
Mon 2 NovVeenendaal Centrum 09:29No data—
Sun 1 NovVeenendaal Centrum 09:380 min—
Sat 31 OctVeenendaal Centrum 09:30+1 min+3 min
Fri 30 OctVeenendaal Centrum 09:29No data—
Thu 29 OctVeenendaal Centrum 09:30No data—
Wed 28 OctVeenendaal Centrum 09:29No data—
Tue 27 OctVeenendaal Centrum 09:29Partial coverage0 min—
Mon 26 OctVeenendaal Centrum 09:32Partial coverage0 min—
Sun 25 OctVeenendaal Centrum 09:29No data—
Sat 24 OctVeenendaal Centrum 09:450 min—
Fri 23 OctBunnik 09:03No data—
Thu 22 OctBunnik 09:07No data—
Wed 21 OctBunnik 09:050 min—
Tue 20 OctBunnik 09:050 min—
Mon 19 OctVeenendaal Centrum 09:31Partial coverage0 min—
Sun 18 OctVeenendaal Centrum 09:290 min+1 min
Sat 17 OctVeenendaal Centrum 09:290 min—
Fri 16 OctVeenendaal Centrum 09:29Partial coverage0 min—
Thu 15 OctVeenendaal Centrum 09:29No data—
Wed 14 OctVeenendaal Centrum 09:29No data—
Tue 13 OctVeenendaal Centrum 09:29No data—
Mon 12 OctVeenendaal Centrum 09:31No data—
Sun 11 OctVeenendaal Centrum 09:310 min—
Sat 10 OctVeenendaal Centrum 09:30+1 min+1 min
Fri 9 OctVeenendaal Centrum 09:29Partial coverage0 min—
Thu 8 OctVeenendaal Centrum 09:29Partial coverage0 min—
Wed 7 OctVeenendaal Centrum 09:29Partial coverage0 min—