Train NS 7333 Breukelen – Rhenen

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

✓ Today’s run finished

Today, last fix heading to Veenendaal Centrum at 10:59 No data

  1. Breukelen09:58
  2. Utrecht Zuilen10:08
  3. Utrecht Centraal10:11
  4. Bunnik10:22
  5. Maarn10:32
  6. Veenendaal Centrum10:44
  7. Rhenen10:51

Next service: tomorrow 09:58 from Breukelen · Fri 6 Nov

Next departure 09:58 tomorrow · Breukelen
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 10 full · 9 partial · 11 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=3
  • 100% T n=4
  • 100% W n=4
  • 100% T n=1
  • 100% F n=1
  • 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, 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 10
09:58on time on time
10:03≈ on time ≈ on time
10:08≈ on time ≈ on time
10:11 / 10:15≈ on time ≈ on time
10:17≈ on time ≈ on time
10:22≈ on time ≈ on time
10:26≈ on time ≈ on time
10:32≈ on time ≈ on time
10:41≈ on time ≈ on time
10:44 / 10:45≈ on time ≈ on time
10: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
Thu 5 NovVeenendaal Centrum 10:59No data—
Wed 4 NovVeenendaal Centrum 10:59Partial coverage0 min—
Tue 3 NovVeenendaal Centrum 10:59No data—
Mon 2 NovVeenendaal Centrum 10:59Partial coverage0 min—
Sun 1 NovVeenendaal Centrum 11:090 min+1 min
Sat 31 OctVeenendaal Centrum 10:590 min—
Fri 30 OctVeenendaal Centrum 10:59No data—
Thu 29 OctVeenendaal Centrum 11:01No data—
Wed 28 OctVeenendaal Centrum 10:59Partial coverage0 min—
Tue 27 OctVeenendaal Centrum 10:59Partial coverage0 min—
Mon 26 OctVeenendaal Centrum 10:59Partial coverage0 min—
Sun 25 OctVeenendaal Centrum 10:59No data—
Sat 24 OctVeenendaal Centrum 11:150 min—
Fri 23 OctBunnik 10:36No data—
Thu 22 OctBunnik 10:38No data—
Wed 21 OctBunnik 10:570 min—
Tue 20 OctBunnik 10:360 min—
Mon 19 OctVeenendaal Centrum 11:07Partial coverage0 min—
Sun 18 OctVeenendaal Centrum 10:590 min—
Sat 17 OctVeenendaal Centrum 10:590 min—
Fri 16 OctVeenendaal Centrum 11:01No data—
Thu 15 OctVeenendaal Centrum 11:05No data—
Wed 14 OctVeenendaal Centrum 10:59No data—
Tue 13 OctVeenendaal Centrum 11:05Partial coverage0 min—
Mon 12 OctVeenendaal Centrum 11:02No data—
Sun 11 OctVeenendaal Centrum 11:010 min—
Sat 10 OctVeenendaal Centrum 10:590 min—
Fri 9 OctVeenendaal Centrum 10:59Partial coverage0 min—
Thu 8 OctVeenendaal Centrum 10:59Partial coverage0 min—
Wed 7 OctMaarn 12:020 min—