Train NS 7372 Rhenen – Breukelen

Rhenen 20:38 → Breukelen 21:30 Daily 0 h 52 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November +2 min

Next service: today 20:38 from Rhenen · Sat 7 Nov

Next departure 20:38 today · Rhenen
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 12 full · 1 partial · 15 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 16 full · 1 partial · 33 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
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 +7 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 67% W n=3
  • 100% T n=2
  • 100% F n=4
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 17 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
20:38on time on time
20:44 / 20:46≈ on time ≈ on time
20:49≈ on time ≈ on time
20:58≈ on time ≈ +1 min
21:04≈ on time ≈ +1 min
21:08≈ on time ≈ +1 min
21:13≈ on time ≈ +1 min
21:16 / 21:19≈ on time ≈ +1 min
21:22≈ on time ≈ +1 min
21:26≈ on time ≈ +2 min
21:30on time +2 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
Fri 6 Nov— 21:34+2 min+2 min
Thu 5 Nov— 21:33No data—
Wed 4 Nov— 21:39+6 min+7 min
Mon 2 Nov— 21:240 min—
Sun 1 NovMaarssen 21:370 min—
Sat 31 OctMaarssen 21:40No data—
Fri 30 Oct— 21:31No data—
Thu 29 Oct— 21:31+1 min+1 min
Wed 28 Oct— 21:340 min—
Tue 27 Oct— 21:32No data—
Mon 26 Oct— 21:35No data—
Sun 25 OctMaarssen 21:41No data—
Sat 24 OctKrommenie-Assendelft 22:360 min—
Fri 23 Oct— 21:32+2 min+2 min
Thu 22 Oct— 21:36No data—
Wed 21 Oct— 21:32No data—
Tue 20 Oct— 21:34No data—
Mon 19 Oct— 21:32No data—
Sun 18 OctMaarn 22:34+1 min—
Sat 17 OctMaarssen 21:41No data—
Fri 16 Oct— 21:31+1 min+1 min
Thu 15 Oct— 21:34No data—
Wed 14 Oct— 21:40No data—
Tue 13 Oct— 21:34No data—
Mon 12 Oct— 21:55No data—
Sun 11 OctMaarssen 21:370 min—
Sat 10 OctMaarssen 21:40Partial coverage+2 min+2 min
Fri 9 Oct— 21:32+1 min—
Thu 8 Oct— 21:320 min—
Wed 7 Oct— 21:310 min—