Train NS 7346 Rhenen – Breukelen

Rhenen 14:08 → Breukelen 15:00 Daily 0 h 52 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 14:08 from Rhenen · Fri 6 Nov

Next departure 14:08 today · Rhenen
On-time · 30 days
85%
11/13 runs under 3 min
RT coverage: 7 full · 6 partial · 16 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 7 full · 9 partial · 72 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sat 31 Oct Max en route +7 min · last fix heading to Krommenie-Assendelft +6 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Krommenie-Assendelft +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
14:08on time on time
14:14 / 14:16≈ on time ≈ +1 min
14:19≈ on time ≈ +1 min
14:28≈ on time ≈ +2 min
14:34≈ on time ≈ +3 min
14:38≈ on time ≈ +3 min
14:43≈ on time ≈ +3 min
14:46 / 14:49≈ on time ≈ +4 min
14:52≈ on time ≈ +4 min
14:56≈ on time ≈ +5 min
15:00on time +5 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 NovMaarssen 15:09Partial coverage0 min—
Wed 4 NovMaarssen 15:09Partial coverage+2 min+2 min
Tue 3 NovMaarssen 15:09No data—
Mon 2 NovMaarssen 15:09No data—
Sun 1 NovMaarssen 15:090 min—
Sat 31 OctKrommenie-Assendelft 16:13+6 min+7 min
Fri 30 OctMaarssen 15:10No data—
Thu 29 OctMaarssen 15:10No data—
Wed 28 OctMaarssen 15:10No data—
Tue 27 OctMaarssen 15:11No data—
Mon 26 OctMaarssen 15:11No data—
Sun 25 OctKrommenie-Assendelft 16:11No data—
Sat 24 OctKrommenie-Assendelft 16:070 min—
Fri 23 OctMaarssen 15:110 min—
Thu 22 OctMaarssen 15:11No data—
Wed 21 OctMaarssen 15:11No data—
Tue 20 OctMaarssen 15:11No data—
Mon 19 OctMaarssen 15:12Partial coverage0 min—
Sun 18 OctKrommenie-Assendelft 16:12+4 min+5 min
Sat 17 OctZaandijk Zaanse Schans 16:05No data—
Fri 16 OctMaarssen 15:11Partial coverage0 min—
Thu 15 OctMaarssen 15:11No data—
Wed 14 OctMaarssen 15:11No data—
Tue 13 OctMaarssen 15:11No data—
Mon 12 OctMaarssen 15:26No data—
Sun 11 OctMaarssen 15:070 min—
Sat 10 OctKrommenie-Assendelft 16:220 min+14 min
Fri 9 OctMaarssen 15:11Partial coverage+1 min+1 min
Thu 8 OctMaarssen 15:11Partial coverage+1 min+1 min
Wed 7 OctMaarssen 15:11Partial coverage+1 min+1 min