Train NS 7334 Rhenen – Breukelen

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

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

Next departure 11:08 today · Rhenen
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 9 full · 11 partial · 9 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 9 full · 12 partial · 67 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: +2 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

Distribution · 90 days

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

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

On-time by weekday

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