Train NS 7341 Breukelen – Rhenen

Breukelen 11:58 → Rhenen 12:51 Daily 0 h 53 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 11:58 from Breukelen · Sun 8 Nov

Next departure 11:58 today · Breukelen
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 9 full · 8 partial · 12 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 9 full · 13 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Rhenen, 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

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

  • Early 0% · 0
  • On time 100% · 22
  • 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=1
  • 100% W n=4
  • 100% T n=4
  • 100% F n=4
  • 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, 22 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:58on time on time
12:03≈ on time ≈ on time
12:08≈ on time ≈ on time
12:11 / 12:14≈ on time ≈ on time
12:16≈ on time ≈ on time
12:21≈ on time ≈ on time
12:25≈ on time ≈ on time
12:31≈ on time ≈ on time
12:40≈ on time ≈ on time
12:43 / 12:45≈ on time ≈ on time
12:51on 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
Sat 7 NovVeenendaal Centrum 12:59Partial coverage0 min—
Fri 6 NovVeenendaal Centrum 12:59No data—
Thu 5 NovVeenendaal Centrum 12:59No data—
Wed 4 NovVeenendaal Centrum 12:59Partial coverage0 min—
Tue 3 NovVeenendaal Centrum 12:59No data—
Mon 2 NovVeenendaal Centrum 12:59No data—
Sun 1 NovVeenendaal Centrum 13:160 min—
Sat 31 OctVeenendaal Centrum 13:00+2 min+2 min
Fri 30 OctVeenendaal Centrum 12:59Partial coverage0 min—
Thu 29 OctVeenendaal Centrum 13:16Partial coverage0 min—
Wed 28 OctVeenendaal Centrum 12:59Partial coverage0 min—
Tue 27 OctVeenendaal Centrum 12:59No data—
Mon 26 OctVeenendaal Centrum 12:59No data—
Sun 25 OctVeenendaal Centrum 13:01No data—
Sat 24 OctVeenendaal Centrum 13:150 min—
Fri 23 OctBunnik 12:330 min—
Thu 22 OctBunnik 12:350 min—
Wed 21 OctBunnik 12:340 min—
Tue 20 OctBunnik 12:34No data—
Mon 19 OctVeenendaal Centrum 12:59Partial coverage0 min—
Sun 18 OctVeenendaal Centrum 12:590 min—
Sat 17 OctVeenendaal Centrum 12:59No data—
Fri 16 OctVeenendaal Centrum 12:59Partial coverage0 min—
Thu 15 OctVeenendaal Centrum 12:59Partial coverage0 min—
Wed 14 OctVeenendaal Centrum 12:59No data—
Tue 13 OctVeenendaal Centrum 13:05No data—
Mon 12 OctVeenendaal Centrum 12:59No data—
Sun 11 OctVeenendaal Centrum 13:010 min—
Sat 10 OctVeenendaal Centrum 12:590 min—
Fri 9 OctVeenendaal Centrum 12:59Partial coverage0 min—