Train NS 7379 Breukelen – Rhenen

Breukelen 21:28 → Rhenen 22:21 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 21:28 from Breukelen · Thu 5 Nov

Next departure 21:28 today · Breukelen
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 14 full · 3 partial · 12 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 16 full · 3 partial · 30 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 Rhenen, 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=3
  • 100% T n=4
  • 100% F n=3
  • 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, 19 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
21:28on time on time
21:33≈ on time ≈ on time
21:38≈ on time ≈ on time
21:41 / 21:44≈ on time ≈ on time
21:46≈ on time ≈ on time
21:51≈ on time ≈ on time
21:55≈ on time ≈ on time
22:01≈ on time ≈ on time
22:10≈ on time ≈ +1 min
22:13 / 22:15≈ on time ≈ +1 min
22:21on 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 Nov— 22:230 min—
Tue 3 Nov— 22:23No data—
Mon 2 Nov— 22:22+1 min+1 min
Sun 1 NovVeenendaal Centrum 22:290 min—
Sat 31 OctVeenendaal Centrum 22:29No data—
Fri 30 Oct— 22:22No data—
Thu 29 Oct— 22:210 min—
Wed 28 Oct— 22:22No data—
Tue 27 Oct— 22:23No data—
Mon 26 Oct— 22:22No data—
Sun 25 OctVeenendaal Centrum 22:29No data—
Sat 24 OctVeenendaal Centrum 22:45No data—
Fri 23 Oct— 21:57+1 min+1 min
Thu 22 Oct— 21:580 min—
Wed 21 Oct— 21:570 min—
Tue 20 Oct— 21:57No data—
Mon 19 Oct— 22:22No data—
Sun 18 OctVeenendaal Centrum 22:29Partial coverage0 min—
Sat 17 OctVeenendaal Centrum 22:30Partial coverage0 min—
Fri 16 Oct— 22:220 min—
Thu 15 Oct— 22:240 min—
Wed 14 Oct— 22:23No data—
Tue 13 Oct— 22:25No data—
Mon 12 Oct— 22:230 min—
Sun 11 OctVeenendaal Centrum 22:310 min—
Sat 10 OctMaarn 22:23Partial coverage0 min—
Fri 9 Oct— 22:25+1 min+2 min
Thu 8 Oct— 22:230 min—
Wed 7 Oct— 22:220 min—
Tue 6 Oct— 22:230 min+1 min