Train NS 7344 Rhenen – Breukelen

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 13:38 from Rhenen · Fri 6 Nov

Next departure 13:38 today · Rhenen
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 11 full · 9 partial · 9 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 11 full · 12 partial · 65 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

Worst days

  • Sat 10 Oct Max en route +6 min · last fix heading to Krommenie-Assendelft +5 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Maarssen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 75% W n=4
  • 100% T n=3
  • 100% F n=2
  • 75% 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, 23 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:38on time on time
13:44 / 13:46≈ on time ≈ on time
13:49≈ on time ≈ on time
13:58≈ on time ≈ on time
14:04≈ on time ≈ on time
14:08≈ on time ≈ on time
14:13≈ on time ≈ on time
14:16 / 14:19≈ on time ≈ on time
14:22≈ on time ≈ on time
14:26≈ on time ≈ on time
14:30on time on time

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 5 NovMaarssen 14:43No data—
Wed 4 NovMaarssen 14:44Partial coverage+5 min+5 min
Tue 3 NovMaarssen 14:39No data—
Mon 2 NovMaarssen 14:39Partial coverage0 min—
Sun 1 NovMaarssen 14:430 min—
Sat 31 OctKrommenie-Assendelft 15:370 min—
Fri 30 OctMaarssen 14:40No data—
Thu 29 OctMaarssen 14:40Partial coverage0 min—
Wed 28 OctMaarssen 14:430 min—
Tue 27 OctUtrecht Vaartsche Rijn 15:00Partial coverage0 min—
Mon 26 OctMaarssen 14:42Partial coverage0 min—
Sun 25 OctZaandijk Zaanse Schans 16:02No data—
Sat 24 OctKrommenie-Assendelft 15:360 min—
Fri 23 OctMaarssen 14:410 min—
Thu 22 OctMaarssen 14:420 min—
Wed 21 OctMaarssen 14:420 min—
Tue 20 OctMaarssen 14:42No data—
Mon 19 OctMaarssen 14:41Partial coverage0 min—
Sun 18 OctKrommenie-Assendelft 15:370 min+1 min
Sat 17 OctZaandijk Zaanse Schans 15:340 min—
Fri 16 OctMaarssen 14:41No data—
Thu 15 OctMaarssen 14:41No data—
Wed 14 OctMaarssen 14:41No data—
Tue 13 OctMaarssen 14:40Partial coverage0 min—
Mon 12 OctMaarssen 14:40No data—
Sun 11 OctMaarssen 14:370 min—
Sat 10 OctKrommenie-Assendelft 15:43+5 min+6 min
Fri 9 OctMaarssen 14:42Partial coverage0 min—
Thu 8 OctMaarssen 14:41Partial coverage+1 min+1 min
Wed 7 OctMaarssen 14:41Partial coverage+1 min—