Train NS 7342 Rhenen – Breukelen

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

✓ Today’s run finished

Today, last fix heading to Maarssen at 14:09 No data

  1. Rhenen13:08
  2. Veenendaal West13:19
  3. Maarn13:28
  4. Bunnik13:38
  5. Utrecht Centraal13:46
  6. Maarssen13:56
  7. Breukelen14:00

Next service: tomorrow 13:08 from Rhenen · Sat 7 Nov

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

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