Train NS 7384 Rhenen – Breukelen

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

It has not run yet today

Last recorded run: Wednesday 4 November +6 min

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

Next departure 23:38 today · Rhenen
On-time · 30 days
78%
14/18 runs under 3 min
RT coverage: 15 full · 3 partial · 5 no data
On-time · 90 days
80%
16/20 runs under 3 min
RT coverage: 16 full · 4 partial · 15 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Fri 9 Oct Max en route +6 min · last fix heading to — +6 min
  • Wed 4 Nov Max en route +6 min · last fix heading to — +6 min
  • Thu 29 Oct Max en route +8 min · last fix heading to — +4 min
  • Wed 7 Oct Max en route +4 min · last fix heading to — +4 min

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 80% · 16
  • 3–10 min 20% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 60% W n=5
  • 50% T n=2
  • 50% F n=2
  • 100% S n=1
  • 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
23:38on time on time
23:44 / 23:46≈ on time ≈ +1 min
23:49≈ on time ≈ +1 min
23:58≈ on time ≈ +2 min
00:04≈ on time ≈ +2 min
00:08≈ on time ≈ +3 min
00:13≈ on time ≈ +3 min
00:16 / 00:19≈ on time ≈ +4 min
00:22≈ on time ≈ +4 min
00:26≈ on time ≈ +5 min
00:30on time +5 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— 00:39+6 min+6 min
Mon 2 Nov— 00:290 min—
Sun 1 NovMaarssen 00:44Partial coverage0 min—
Thu 29 Oct— 00:38+4 min+8 min
Wed 28 Oct— 00:320 min—
Tue 27 Oct— 00:360 min—
Mon 26 Oct— 00:310 min—
Sun 25 OctMaarssen 00:41No data—
Sat 24 Oct— 01:28No data—
Wed 21 Oct— 00:310 min—
Mon 19 Oct— 00:360 min—
Sun 18 OctMaarssen 00:41Partial coverage+1 min+1 min
Sat 17 OctMaarssen 00:40No data—
Fri 16 Oct— 00:35+2 min+2 min
Thu 15 Oct— 00:32No data—
Wed 14 Oct— 00:320 min—
Tue 13 Oct— 00:34No data—
Mon 12 Oct— 00:34+1 min—
Sun 11 OctMaarssen 00:37Partial coverage0 min—
Sat 10 Oct— 00:320 min—
Fri 9 Oct— 00:44+6 min+6 min
Thu 8 Oct— 00:310 min—
Wed 7 Oct— 00:32+4 min+4 min
Tue 6 Oct— 00:34+2 min+2 min
Mon 5 OctBunnik 00:31Partial coverage+1 min—
Sun 4 OctMaarssen 00:41No data—
Sat 3 OctBreukelen 00:45No data—
Sun 27 SeptMaarssen 00:41No data—
Sat 26 SeptRhenen 23:52No data—
Sun 20 SeptMaarssen 00:41No data—