Train NS 7356 Rhenen – Breukelen

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

It has not run yet today

Last recorded run: Saturday 7 November +2 min

Next service: today 16:38 from Rhenen · Sun 8 Nov

Next departure 16:38 today · Rhenen
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 9 full · 6 partial · 14 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 9 full · 11 partial · 68 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 +11 min · last fix heading to Krommenie-Assendelft +11 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Krommenie-Assendelft +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=3
  • 100% F n=3
  • 80% S n=5
  • 50% S n=2

Stops and timetable

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

Last 90 days, 20 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:38on time on time
16:44 / 16:46≈ on time ≈ +1 min
16:49≈ on time ≈ +1 min
16:58≈ on time ≈ +2 min
17:04≈ on time ≈ +3 min
17:08≈ on time ≈ +3 min
17:13≈ on time ≈ +4 min
17:16 / 17:19≈ on time ≈ +4 min
17:22≈ on time ≈ +4 min
17:26≈ on time ≈ +5 min
17:30on 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
Sat 7 NovMaarssen 17:39Partial coverage+2 min+2 min
Fri 6 NovMaarssen 17:39Partial coverage0 min—
Thu 5 NovMaarssen 17:39Partial coverage0 min—
Wed 4 NovMaarssen 17:39No data—
Tue 3 NovMaarssen 17:39No data—
Mon 2 NovMaarssen 17:39No data—
Sun 1 NovMaarssen 17:37No data—
Sat 31 OctKrommenie-Assendelft 18:37+1 min+1 min
Fri 30 OctMaarssen 17:40No data—
Thu 29 OctMaarssen 17:34No data—
Wed 28 OctMaarssen 17:40No data—
Tue 27 OctMaarssen 17:40Partial coverage0 min—
Mon 26 OctMaarssen 17:40No data—
Sun 25 OctKrommenie-Assendelft 18:38No data—
Sat 24 OctKrommenie-Assendelft 18:370 min—
Fri 23 OctMaarssen 17:410 min—
Thu 22 OctMaarssen 17:400 min—
Wed 21 OctMaarssen 17:410 min—
Tue 20 OctMaarssen 17:40No data—
Mon 19 OctMaarssen 17:40Partial coverage0 min—
Sun 18 OctKrommenie-Assendelft 18:39+4 min+4 min
Sat 17 OctZaandijk Zaanse Schans 18:340 min—
Fri 16 OctMaarssen 17:41No data—
Thu 15 OctMaarssen 17:40No data—
Wed 14 OctMaarssen 17:41No data—
Tue 13 OctMaarssen 17:40No data—
Mon 12 OctMaarssen 17:40Partial coverage0 min—
Sun 11 OctMaarssen 17:38+1 min+1 min
Sat 10 OctKrommenie-Assendelft 18:47+11 min+11 min
Fri 9 OctMaarssen 17:40Partial coverage0 min—