Train NS 7338 Rhenen – Breukelen

Rhenen 12:08 → Breukelen 13:00 Daily 0 h 52 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 12:08 from Rhenen · Sun 8 Nov

Next departure 12:08 today · Rhenen
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 10 full · 9 partial · 10 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 10 full · 14 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

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

  • Early 0% · 0
  • On time 100% · 24
  • 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=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

Last 90 days, 24 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
12:08on time on time
12:14 / 12:16≈ on time ≈ on time
12:19≈ on time ≈ on time
12:28≈ on time ≈ +1 min
12:34≈ on time ≈ +1 min
12:38≈ on time ≈ +1 min
12:43≈ on time ≈ +1 min
12:46 / 12:49≈ on time ≈ +1 min
12:52≈ on time ≈ +1 min
12:56≈ on time ≈ +1 min
13:00on time +2 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
Sat 7 NovMaarssen 13:09Partial coverage0 min—
Fri 6 NovMaarssen 13:19No data—
Thu 5 NovMaarssen 13:24Partial coverage0 min—
Wed 4 NovMaarssen 13:09Partial coverage+2 min+2 min
Tue 3 NovMaarssen 13:09Partial coverage0 min—
Mon 2 NovMaarssen 13:09No data—
Sun 1 NovMaarssen 13:100 min—
Sat 31 OctKrommenie-Assendelft 14:10+3 min+3 min
Fri 30 OctMaarssen 13:11Partial coverage0 min—
Thu 29 OctMaarssen 13:15No data—
Wed 28 OctMaarssen 13:25No data—
Tue 27 OctMaarssen 13:11Partial coverage0 min—
Mon 26 OctMaarssen 13:11Partial coverage0 min—
Sun 25 OctKrommenie-Assendelft 14:12No data—
Sat 24 OctKrommenie-Assendelft 14:070 min—
Fri 23 OctMaarssen 13:100 min—
Thu 22 OctMaarssen 13:130 min—
Wed 21 OctMaarssen 13:110 min—
Tue 20 OctMaarssen 13:11No data—
Mon 19 OctMaarssen 13:11Partial coverage0 min—
Sun 18 OctKrommenie-Assendelft 14:080 min—
Sat 17 OctZaandijk Zaanse Schans 14:050 min—
Fri 16 OctMaarssen 13:11No data—
Thu 15 OctMaarssen 13:18No data—
Wed 14 OctMaarssen 13:11No data—
Tue 13 OctMaarssen 13:10No data—
Mon 12 OctMaarssen 13:11Partial coverage0 min—
Sun 11 OctMaarssen 13:070 min—
Sat 10 OctKrommenie-Assendelft 14:08+1 min+1 min
Fri 9 OctMaarssen 13:12Partial coverage+2 min+2 min