Train NS 7353 Breukelen – Rhenen

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 14:58 from Breukelen · Fri 6 Nov

Next departure 14:58 today · Breukelen
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 10 full · 10 partial · 9 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 10 full · 13 partial · 65 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

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

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