Train NS 7375 Breukelen – Rhenen

Breukelen 20:28 → Rhenen 21:21 Daily 0 h 53 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 20:28 from Breukelen · Thu 19 Nov

Next departure 20:28 today · Breukelen
On-time · 30 days
83%
19/23 runs under 3 min
RT coverage: 18 full · 5 partial · 5 no data
On-time · 90 days
79%
27/34 runs under 3 min
RT coverage: 26 full · 8 partial · 23 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: +3 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

Worst days

  • Fri 16 Oct Max en route +11 min · last fix heading to — +11 min
  • Tue 6 Oct Max en route +6 min · last fix heading to — +6 min
  • Sun 15 Nov Max en route +7 min · last fix heading to Veenendaal Centrum +6 min
  • Mon 16 Nov Max en route +4 min · last fix heading to — +4 min
  • Thu 12 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 27
  • 3–10 min 18% · 6
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 60% T n=5
  • 100% W n=5
  • 67% T n=3
  • 60% F n=5
  • 100% S n=6
  • 80% S n=5

Stops and timetable

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

Last 90 days, 34 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:28on time on time
20:33≈ on time ≈ +1 min
20:38≈ on time ≈ +1 min
20:41 / 20:44≈ on time ≈ +1 min
20:46≈ on time ≈ +2 min
20:51≈ on time ≈ +2 min
20:55≈ on time ≈ +2 min
21:01≈ on time ≈ +3 min
21:10≈ on time ≈ +3 min
21:13 / 21:15≈ on time ≈ +3 min
21:21on time +4 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 18 Nov— 21:230 min—
Tue 17 Nov— 21:24+3 min+3 min
Mon 16 Nov— 21:29+4 min+4 min
Sun 15 NovVeenendaal Centrum 21:34Partial coverage+6 min+7 min
Sat 14 NovVeenendaal Centrum 21:29Partial coverage0 min—
Fri 13 Nov— 21:22+1 min—
Thu 12 Nov— 21:29+4 min+4 min
Wed 11 Nov— 21:23+1 min+1 min
Tue 10 Nov— 21:220 min—
Mon 9 Nov— 21:220 min—
Sun 8 NovVeenendaal Centrum 21:29Partial coverage0 min—
Sat 7 NovVeenendaal Centrum 21:29Partial coverage0 min—
Fri 6 Nov— 21:220 min—
Thu 5 Nov— 21:290 min—
Wed 4 Nov— 21:24+1 min+3 min
Tue 3 Nov— 21:27No data—
Mon 2 Nov— 21:220 min—
Sun 1 NovVeenendaal Centrum 21:290 min—
Sat 31 OctVeenendaal Centrum 21:29Partial coverage0 min—
Thu 29 Oct— 21:210 min+2 min
Wed 28 Oct— 21:22No data—
Tue 27 Oct— 21:250 min—
Mon 26 Oct— 21:22No data—
Sun 25 OctVeenendaal Centrum 21:29No data—
Sat 24 OctVeenendaal Centrum 21:450 min—
Fri 23 Oct— 20:58+2 min+2 min
Thu 22 Oct— 20:57No data—
Wed 21 Oct— 20:570 min—
Tue 20 Oct— 20:570 min—
Mon 19 Oct— 21:23No data—