Train NS 7362 Rhenen – Breukelen

Rhenen 18:08 → Breukelen 19:01 Daily 0 h 53 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 18:08 from Rhenen · Thu 5 Nov

Next departure 18:08 today · Rhenen
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 17 full · 4 partial · 7 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 19 full · 4 partial · 56 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: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 23
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=5
  • 100% T n=3
  • 100% F n=2
  • 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, 23 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
18:08on time on time
18:14 / 18:16≈ on time ≈ on time
18:19≈ on time ≈ on time
18:28≈ on time ≈ +1 min
18:33≈ on time ≈ +1 min
18:38≈ on time ≈ +1 min
18:42≈ on time ≈ +1 min
18:45 / 18:49≈ on time ≈ +1 min
18:52≈ on time ≈ +1 min
18:57≈ on time ≈ +1 min
19:01on 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
Wed 4 NovRhenen 19:02Partial coverage0 min—
Tue 3 NovRhenen 19:050 min—
Mon 2 NovRhenen 18:59+1 min+1 min
Sun 1 NovMaarssen 19:090 min—
Sat 31 OctMaarssen 19:11+1 min+1 min
Fri 30 OctUtrecht Zuilen 19:06No data—
Wed 28 OctRhenen 19:25Partial coverage0 min—
Tue 27 Oct— 19:070 min—
Mon 26 OctRhenen 19:130 min—
Sun 25 OctMaarssen 19:11No data—
Sat 24 OctKrommenie-Assendelft 20:070 min—
Fri 23 OctMaarssen 19:10+1 min—
Thu 22 OctUtrecht Vaartsche Rijn 19:040 min—
Wed 21 OctBunnik 19:020 min—
Tue 20 OctUtrecht Vaartsche Rijn 19:11No data—
Mon 19 OctUtrecht Vaartsche Rijn 19:02No data—
Sun 18 OctMaarssen 19:11+1 min+1 min
Sat 17 OctMaarssen 19:11No data—
Fri 16 OctMaarssen 19:10No data—
Thu 15 OctMaarn 19:040 min—
Wed 14 OctMaarssen 19:09Partial coverage0 min—
Tue 13 OctBunnik 19:04No data—
Mon 12 OctUtrecht Vaartsche Rijn 19:020 min—
Sun 11 OctMaarssen 19:09+3 min+3 min
Sat 10 OctMaarssen 19:110 min—
Fri 9 OctDriebergen-Zeist 19:010 min—
Thu 8 Oct— 19:04+1 min+1 min
Wed 7 OctRhenen 18:22Partial coverage0 min—
Tue 6 Oct— 19:04+1 min+1 min
Mon 5 OctRhenen 19:02+1 min—