Train NS 7347 Breukelen – Rhenen

Breukelen 13:28 → Rhenen 14:21 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 13:28 from Breukelen · Sun 8 Nov

Next departure 13:28 today · Breukelen
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 9 full · 7 partial · 13 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 9 full · 12 partial · 67 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 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=3
  • 100% T n=4
  • 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, 21 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:28on time on time
13:33≈ on time ≈ on time
13:38≈ on time ≈ on time
13:41 / 13:44≈ on time ≈ on time
13:46≈ on time ≈ on time
13:51≈ on time ≈ on time
13:55≈ on time ≈ on time
14:01≈ on time ≈ on time
14:10≈ on time ≈ +1 min
14:13 / 14:15≈ on time ≈ +1 min
14:21on 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 NovVeenendaal Centrum 14:29Partial coverage0 min—
Fri 6 NovVeenendaal Centrum 14:29No data—
Thu 5 NovVeenendaal Centrum 14:34Partial coverage0 min—
Wed 4 NovVeenendaal Centrum 14:29Partial coverage0 min—
Tue 3 NovVeenendaal Centrum 14:34No data—
Mon 2 NovVeenendaal Centrum 14:29No data—
Sun 1 NovVeenendaal Centrum 15:000 min—
Sat 31 OctVeenendaal Centrum 14:290 min+1 min
Fri 30 OctVeenendaal Centrum 14:29No data—
Thu 29 OctVeenendaal Centrum 14:29Partial coverage0 min—
Wed 28 OctVeenendaal Centrum 14:29No data—
Tue 27 OctVeenendaal Centrum 14:29Partial coverage0 min—
Mon 26 OctVeenendaal Centrum 14:29Partial coverage0 min—
Sun 25 OctVeenendaal Centrum 14:43No data—
Sat 24 OctVeenendaal Centrum 14:450 min—
Fri 23 OctBunnik 14:040 min—
Thu 22 OctBunnik 14:050 min—
Wed 21 OctBunnik 14:040 min—
Tue 20 OctBunnik 14:05No data—
Mon 19 OctVeenendaal Centrum 14:29Partial coverage0 min—
Sun 18 OctVeenendaal Centrum 14:30+1 min+3 min
Sat 17 OctVeenendaal Centrum 14:31No data—
Fri 16 OctVeenendaal Centrum 14:29No data—
Thu 15 OctVeenendaal Centrum 14:30No data—
Wed 14 OctVeenendaal Centrum 14:29No data—
Tue 13 OctVeenendaal Centrum 14:29No data—
Mon 12 OctVeenendaal Centrum 14:29No data—
Sun 11 OctVeenendaal Centrum 14:31+1 min—
Sat 10 OctVeenendaal Centrum 14:290 min—
Fri 9 OctVeenendaal Centrum 14:29Partial coverage+1 min+1 min