Train NS 7322 Rhenen – Breukelen

Rhenen 08:08 → Breukelen 09:00 Daily 0 h 52 min · 11 stops NS (Nederlandse Spoorwegen)

Running now · updated 09:02

Position estimated from the timetable

Heading to Breukelen 0 min

Estimated arrival at Breukelen 09:00 · 16 km/h

  1. Rhenen08:08
  2. Veenendaal West08:19
  3. Maarn08:28
  4. Bunnik08:38
  5. Utrecht Centraal08:46
  6. Utrecht Zuilen08:52
  7. Breukelen09:00

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

On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 5 full · 13 partial · 12 no data
On-time · 90 days
98%
55/56 runs under 3 min
RT coverage: 37 full · 19 partial · 33 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: +2 min

Last 30 days

Arrival delay at Breukelen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 4 Nov Max en route +5 min · last fix heading to Maarssen +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 55
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=10
  • 90% W n=10
  • 100% T n=9
  • 100% F n=7
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 56 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
08:08on time on time
08:14 / 08:16≈ on time ≈ on time
08:19≈ on time ≈ on time
08:28≈ on time ≈ on time
08:34≈ on time ≈ on time
08:38≈ on time ≈ on time
08:43≈ on time ≈ on time
08:46 / 08:49≈ on time ≈ on time
08:52≈ on time ≈ on time
08:56≈ on time ≈ on time
09:00on 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
Wed 11 NovMaarssen 08:59Partial coverage0 min+2 min
Tue 10 NovMaarssen 09:09Partial coverage+1 min+1 min
Mon 9 NovMaarssen 09:09Partial coverage+1 min—
Sun 8 NovMaarssen 09:09Partial coverage+2 min+2 min
Sat 7 NovMaarssen 09:09Partial coverage+2 min+2 min
Fri 6 NovMaarssen 09:12No data—
Thu 5 NovMaarssen 09:09No data—
Wed 4 NovMaarssen 09:14Partial coverage+5 min+5 min
Tue 3 NovMaarssen 09:12Partial coverage0 min—
Mon 2 NovMaarssen 09:120 min—
Sun 1 NovMaarssen 09:060 min+2 min
Sat 31 OctMaarssen 09:10Partial coverage+1 min+1 min
Fri 30 OctMaarssen 09:11Partial coverage0 min—
Thu 29 OctMaarssen 09:12Partial coverage0 min—
Wed 28 OctMaarssen 09:11Partial coverage0 min—
Tue 27 OctMaarssen 09:11No data—
Mon 26 OctMaarssen 09:13No data—
Sun 25 OctMaarssen 09:10No data—
Sat 24 OctMaarssen 08:590 min—
Fri 23 OctMaarssen 09:110 min—
Thu 22 OctMaarssen 09:11No data—
Wed 21 OctMaarssen 09:11No data—
Tue 20 OctMaarssen 09:110 min—
Mon 19 OctMaarssen 09:11No data—
Sun 18 OctMaarssen 09:11Partial coverage+1 min—
Sat 17 OctMaarssen 09:11Partial coverage+1 min+1 min
Fri 16 OctMaarssen 09:10No data—
Thu 15 OctMaarssen 09:10No data—
Wed 14 OctMaarssen 09:11No data—
Tue 13 OctMaarssen 09:12No data—