Train NS 7380 Rhenen – Breukelen

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

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 22:38 from Rhenen · Thu 5 Nov

Next departure 22:38 today · Rhenen
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 14 full · 2 partial · 11 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 16 full · 2 partial · 29 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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 14 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
22:38on time on time
22:44 / 22:46≈ on time ≈ on time
22:49≈ on time ≈ +1 min
22:58≈ on time ≈ +1 min
23:04≈ +1 min ≈ +1 min
23:08≈ +1 min ≈ +2 min
23:13≈ +1 min ≈ +2 min
23:16 / 23:19≈ +1 min ≈ +2 min
23:22≈ +1 min ≈ +2 min
23:26≈ +1 min ≈ +2 min
23:30+1 min +3 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
Wed 4 Nov— 23:32+1 min—
Mon 2 Nov— 23:29+1 min—
Sun 1 NovMaarssen 23:380 min—
Sat 31 OctUtrecht Zuilen 23:36No data—
Fri 30 Oct— 23:34No data—
Wed 28 Oct— 23:31No data—
Tue 27 Oct— 23:32No data—
Mon 26 Oct— 23:32No data—
Sun 25 OctMaarssen 23:41No data—
Sat 24 OctVeenendaal West 00:280 min—
Fri 23 Oct— 23:36+2 min+2 min
Thu 22 Oct— 23:31No data—
Wed 21 Oct— 23:39No data—
Tue 20 Oct— 23:34No data—
Mon 19 Oct— 23:32No data—
Sun 18 OctMaarssen 23:40Partial coverage0 min—
Sat 17 OctMaarssen 23:41Partial coverage0 min—
Fri 16 Oct— 23:35+2 min+2 min
Thu 15 Oct— 23:340 min—
Wed 14 Oct— 23:37+5 min+5 min
Tue 13 Oct— 23:32No data—
Mon 12 Oct— 23:32+1 min—
Sun 11 OctMaarssen 23:37+1 min+1 min
Sat 10 Oct— 23:32+1 min+1 min
Fri 9 Oct— 23:37+3 min+3 min
Thu 8 Oct— 23:32+1 min—
Wed 7 Oct— 23:32+1 min+1 min
Tue 6 Oct— 23:36+2 min+2 min
Mon 5 Oct— 23:31+1 min+1 min
Sun 4 OctBreukelen 23:47No data—