Train NS 7321 Breukelen – Rhenen

Breukelen 06:58 → Rhenen 07:51 Mon, Tue, Wed, Thu, Fri, Sat 0 h 53 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 06:58 from Breukelen · Tue 10 Nov

Next departure 06:58 today · Breukelen
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 8 full · 14 partial · 3 no data
On-time · 90 days
98%
55/56 runs under 3 min
RT coverage: 38 full · 18 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Mon 12 Oct Max en route +6 min · last fix heading to Breukelen +6 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 96% · 54
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 90% M n=10
  • 100% T n=12
  • 100% W n=10
  • 100% T n=9
  • 100% F n=10
  • 100% S n=5
  • — S n=0

Stops and timetable

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

Last 90 days, 56 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
06:58on time on time
07:03≈ on time ≈ on time
07:08≈ on time ≈ on time
07:11 / 07:14≈ on time ≈ on time
07:16≈ on time ≈ on time
07:21≈ on time ≈ on time
07:25≈ on time ≈ on time
07:31≈ on time ≈ on time
07:40≈ on time ≈ on time
07:43 / 07:45≈ on time ≈ on time
07:51on time on time

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
Mon 9 NovVeenendaal Centrum 07:59Partial coverage0 min—
Sat 7 NovVeenendaal Centrum 08:000 min—
Fri 6 NovVeenendaal Centrum 08:02No data—
Thu 5 NovVeenendaal Centrum 07:59No data—
Wed 4 NovVeenendaal Centrum 07:59Partial coverage0 min—
Tue 3 NovVeenendaal Centrum 07:59Partial coverage0 min—
Mon 2 NovVeenendaal Centrum 07:59No data—
Sat 31 OctVeenendaal Centrum 07:590 min—
Fri 30 OctVeenendaal Centrum 07:59Partial coverage0 min—
Thu 29 OctVeenendaal Centrum 07:59Partial coverage0 min—
Wed 28 OctVeenendaal Centrum 07:59Partial coverage0 min—
Tue 27 OctVeenendaal Centrum 07:59Partial coverage0 min—
Mon 26 OctVeenendaal Centrum 07:59Partial coverage0 min—
Sat 24 OctVeenendaal Centrum 08:150 min—
Fri 23 OctBunnik 07:33+2 min+2 min
Thu 22 OctBunnik 07:350 min—
Wed 21 OctBunnik 07:350 min—
Tue 20 OctBunnik 07:350 min—
Mon 19 OctVeenendaal Centrum 08:00Partial coverage0 min—
Sat 17 OctVeenendaal Centrum 07:590 min—
Fri 16 OctVeenendaal Centrum 08:00Partial coverage0 min—
Thu 15 OctVeenendaal Centrum 07:59Partial coverage0 min—
Wed 14 OctVeenendaal Centrum 07:59Partial coverage0 min—
Tue 13 OctVeenendaal Centrum 07:59Partial coverage0 min—
Mon 12 OctBreukelen 08:17Partial coverage+6 min+6 min
Sat 10 OctVeenendaal Centrum 08:01+3 min+4 min
Fri 9 OctVeenendaal Centrum 07:59Partial coverage0 min—
Thu 8 OctVeenendaal Centrum 07:59Partial coverage0 min—
Wed 7 OctVeenendaal Centrum 07:59Partial coverage0 min—
Tue 6 OctVeenendaal Centrum 07:59Partial coverage0 min—