Train NS 7358 Rhenen – Breukelen

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

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 17:08 from Rhenen · Sat 7 Nov

Next departure 17:08 today · Rhenen
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 8 full · 6 partial · 15 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 8 full · 10 partial · 70 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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 +3 min · last fix heading to Krommenie-Assendelft +3 min
  • Sat 31 Oct Max en route +3 min · last fix heading to Krommenie-Assendelft +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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