Train NS 7349 Breukelen – Rhenen

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

Running now · updated 14:10

Heading to Rhenen 0 min

Estimated arrival at Rhenen 14:51 · 31 km/h

  1. Breukelen13:58
  2. Utrecht Zuilen14:08
  3. Utrecht Centraal14:11
  4. Bunnik14:21
  5. Maarn14:31
  6. Veenendaal West14:40
  7. Rhenen14:51

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 16 runs arrived on time.

On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 10 full · 6 partial · 14 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 10 full · 10 partial · 69 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

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

  • Early 0% · 0
  • On time 100% · 20
  • 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=3
  • 100% T n=4
  • 100% F n=2
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

Last 90 days, 20 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 10Today
13:58on time on time
14:03≈ on time ≈ on time
14:08≈ on time ≈ on time
14:11 / 14:14≈ on time ≈ on time
14:16≈ on time ≈ on time
14:21≈ on time ≈ on time
14:25≈ on time ≈ on time
14:31≈ on time ≈ on time
14:40≈ on time ≈ +1 min
14:43 / 14:45≈ on time ≈ +1 min
14: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
Sat 7 NovUtrecht Centraal 14:09Partial coverage0 min—
Fri 6 NovVeenendaal Centrum 14:59No data—
Thu 5 NovVeenendaal Centrum 14:59Partial coverage0 min—
Wed 4 NovVeenendaal Centrum 14:59Partial coverage0 min—
Tue 3 NovVeenendaal Centrum 14:59No data—
Mon 2 NovVeenendaal Centrum 14:59No data—
Sun 1 NovVeenendaal Centrum 15:050 min—
Sat 31 OctVeenendaal Centrum 15:00+1 min+2 min
Fri 30 OctVeenendaal Centrum 14:59No data—
Thu 29 OctVeenendaal Centrum 15:14No data—
Wed 28 OctVeenendaal Centrum 14:59No data—
Tue 27 OctVeenendaal Centrum 14:59No data—
Mon 26 OctVeenendaal Centrum 14:59No data—
Sun 25 OctVeenendaal Centrum 14:59No data—
Sat 24 OctVeenendaal Centrum 15:150 min—
Fri 23 OctBunnik 14:340 min—
Thu 22 OctBunnik 14:350 min—
Wed 21 OctBunnik 14:350 min—
Tue 20 OctBunnik 14:34No data—
Mon 19 OctVeenendaal Centrum 14:59Partial coverage0 min—
Sun 18 OctVeenendaal Centrum 14:590 min—
Sat 17 OctVeenendaal Centrum 14:590 min—
Fri 16 OctVeenendaal Centrum 14:59No data—
Thu 15 OctVeenendaal Centrum 15:01Partial coverage0 min—
Wed 14 OctVeenendaal Centrum 15:00No data—
Tue 13 OctVeenendaal Centrum 14:59No data—
Mon 12 OctVeenendaal Centrum 14:59No data—
Sun 11 OctVeenendaal Centrum 15:010 min—
Sat 10 OctVeenendaal Centrum 14:59+1 min—
Fri 9 OctVeenendaal Centrum 14:59Partial coverage0 min—