Train NS 7348 Rhenen – Breukelen

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

It has not run yet today

Last recorded run: Thursday 19 November +4 min

Next service: today 14:38 from Rhenen · Fri 20 Nov

Next departure 14:38 today · Rhenen
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 5 full · 16 partial · 8 no data
On-time · 90 days
90%
28/31 runs under 3 min
RT coverage: 8 full · 23 partial · 57 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

Worst days

  • Sat 31 Oct Max en route +6 min · last fix heading to Krommenie-Assendelft +6 min
  • Thu 19 Nov Max en route +4 min · last fix heading to Maarssen +4 min
  • Sun 18 Oct Max en route +5 min · last fix heading to Krommenie-Assendelft +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 28
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 100% W n=4
  • 75% T n=4
  • 100% F n=3
  • 80% S n=5
  • 80% S n=5

Stops and timetable

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

Last 90 days, 31 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
14:38on time on time
14:44 / 14:46≈ on time ≈ +1 min
14:49≈ on time ≈ +1 min
14:58≈ +1 min ≈ +2 min
15:04≈ +1 min ≈ +2 min
15:08≈ +1 min ≈ +3 min
15:13≈ +1 min ≈ +3 min
15:16 / 15:19≈ +1 min ≈ +3 min
15:22≈ +1 min ≈ +4 min
15:26≈ +1 min ≈ +4 min
15:30+1 min +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
Thu 19 NovMaarssen 15:42Partial coverage+4 min+4 min
Wed 18 NovMaarssen 15:39Partial coverage+1 min—
Tue 17 NovMaarssen 15:39Partial coverage+1 min—
Mon 16 NovMaarssen 15:55Partial coverage+1 min+1 min
Sun 15 NovKrommenie-Assendelft 16:38+1 min+2 min
Sat 14 NovKrommenie-Assendelft 16:39+2 min+2 min
Fri 13 NovMaarssen 15:39Partial coverage+1 min—
Thu 12 NovMaarssen 15:39Partial coverage+1 min+1 min
Wed 11 NovMaarssen 15:39Partial coverage+1 min+1 min
Tue 10 NovMaarssen 15:39Partial coverage+1 min—
Mon 9 NovMaarssen 15:39Partial coverage+1 min—
Sun 8 NovMaarssen 15:39Partial coverage+1 min+1 min
Sat 7 NovMaarssen 15:39Partial coverage+1 min+1 min
Fri 6 NovMaarssen 15:39No data—
Thu 5 NovMaarssen 15:40Partial coverage0 min—
Wed 4 NovMaarssen 15:39Partial coverage0 min—
Tue 3 NovMaarssen 15:39No data—
Mon 2 NovMaarssen 15:39No data—
Sun 1 NovMaarssen 15:390 min—
Sat 31 OctKrommenie-Assendelft 16:43+6 min+6 min
Fri 30 OctMaarssen 15:41Partial coverage0 min—
Thu 29 OctUtrecht Vaartsche Rijn 16:08No data—
Wed 28 OctMaarssen 15:40No data—
Tue 27 OctMaarssen 15:41Partial coverage0 min—
Mon 26 OctMaarssen 15:41Partial coverage0 min—
Sun 25 OctKrommenie-Assendelft 16:37No data—
Sat 24 OctKrommenie-Assendelft 16:37+1 min—
Fri 23 OctMaarssen 15:42No data—
Thu 22 OctMaarssen 15:42No data—
Wed 21 OctMaarssen 15:42No data—