Train NS 7318 Rhenen – Breukelen

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

Running now · updated 07:27

Heading to Breukelen No data

Estimated arrival at Breukelen 08:00 · 135 km/h

  1. Rhenen07:08
  2. Veenendaal West07:19
  3. Maarn07:28
  4. Bunnik07:38
  5. Utrecht Centraal07:46
  6. Utrecht Zuilen07:52
  7. Breukelen08:00
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 7 full · 17 partial · 6 no data
On-time · 90 days
98%
49/50 runs under 3 min
RT coverage: 31 full · 19 partial · 39 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: +2 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

  • Sat 31 Oct Max en route +13 min · last fix heading to Maarssen +13 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 49
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=8
  • 100% W n=8
  • 100% T n=10
  • 100% F n=8
  • 75% S n=4
  • 100% S n=3

Stops and timetable

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

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