Train NS 7330 Rhenen – Breukelen

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

✓ Today’s run finished

Today, last fix heading to Maarssen at 11:09 +2 min

  1. Rhenen10:08
  2. Veenendaal West10:19
  3. Maarn10:28
  4. Bunnik10:38
  5. Utrecht Centraal10:46
  6. Maarssen10:56
  7. Breukelen11:00

Next service: tomorrow 10:08 from Rhenen · Sun 8 Nov

Next departure 10:08 tomorrow · Rhenen
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 5 full · 12 partial · 13 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 6 full · 14 partial · 69 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

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

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

On-time by weekday

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

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
10:08on time on time
10:14 / 10:16≈ on time ≈ on time
10:19≈ on time ≈ on time
10:28≈ on time ≈ on time
10:34≈ on time ≈ +1 min
10:38≈ on time ≈ +1 min
10:43≈ on time ≈ +1 min
10:46 / 10:49≈ on time ≈ +1 min
10:52≈ on time ≈ +1 min
10:56≈ on time ≈ +1 min
11: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
Sat 7 NovMaarssen 11:09Partial coverage+2 min+2 min
Fri 6 NovMaarssen 11:09No data—
Thu 5 NovMaarssen 11:09Partial coverage0 min—
Wed 4 NovMaarssen 11:09Partial coverage+1 min+1 min
Tue 3 NovMaarssen 11:09No data—
Mon 2 NovMaarssen 11:09No data—
Sun 1 NovMaarssen 11:060 min—
Sat 31 OctMaarssen 11:11Partial coverage+1 min—
Fri 30 OctMaarssen 11:10No data—
Thu 29 OctMaarssen 11:11No data—
Wed 28 OctMaarssen 11:11Partial coverage0 min—
Tue 27 OctMaarssen 11:11No data—
Mon 26 OctMaarssen 11:11No data—
Sun 25 OctMaarssen 11:10No data—
Sat 24 OctMaarssen 11:00+1 min+1 min
Fri 23 OctMaarssen 11:11No data—
Thu 22 OctMaarssen 11:11No data—
Wed 21 OctMaarssen 11:350 min—
Tue 20 OctMaarssen 11:140 min—
Mon 19 OctMaarssen 11:10Partial coverage0 min—
Sun 18 OctMaarssen 11:12Partial coverage+2 min+2 min
Sat 17 OctMaarssen 11:11Partial coverage0 min—
Fri 16 OctMaarssen 11:11No data—
Thu 15 OctMaarssen 11:11Partial coverage0 min—
Wed 14 OctMaarssen 11:11No data—
Tue 13 OctMaarssen 11:11No data—
Mon 12 OctMaarssen 11:10Partial coverage0 min—
Sun 11 OctMaarssen 11:07+2 min+2 min
Sat 10 OctMaarssen 11:10Partial coverage0 min—
Fri 9 OctMaarssen 11:10Partial coverage+2 min+2 min