Train NS 7354 Rhenen – Breukelen

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 16:08 from Rhenen · Thu 5 Nov

Next departure 16:08 today · Rhenen
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 9 full · 6 partial · 14 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 9 full · 8 partial · 71 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

Worst days

  • Sat 10 Oct Max en route +4 min · last fix heading to Krommenie-Assendelft +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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