Train NS 7389 Breukelen – Rhenen

Breukelen 23:58 → Rhenen 00:51 Daily 0 h 53 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 23:58 from Breukelen · Fri 6 Nov

Next departure 23:58 today · Breukelen
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 17 full · 3 partial · 4 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 19 full · 4 partial · 14 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

  • Fri 16 Oct Max en route +7 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=5
  • 100% T n=2
  • 50% F n=2
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 23 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
23:58on time on time
00:03≈ on time ≈ on time
00:08≈ on time ≈ on time
00:11 / 00:14≈ on time ≈ on time
00:16≈ on time ≈ on time
00:21≈ on time ≈ on time
00:25≈ on time ≈ on time
00:31≈ on time ≈ on time
00:40≈ on time ≈ +1 min
00:43 / 00:45≈ on time ≈ +1 min
00:51on 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
Thu 5 Nov— 00:52No data—
Wed 4 Nov— 00:530 min—
Mon 2 Nov— 00:520 min—
Sat 31 Oct— 01:03No data—
Fri 30 Oct— 00:52No data—
Wed 28 Oct— 00:530 min—
Tue 27 Oct— 00:520 min—
Mon 26 Oct— 00:520 min—
Sun 25 OctVeenendaal Centrum 00:59Partial coverage0 min—
Sat 24 Oct— 01:080 min—
Thu 22 Oct— 00:260 min—
Wed 21 Oct— 00:260 min—
Tue 20 Oct— 00:290 min—
Mon 19 Oct— 00:530 min—
Sun 18 OctVeenendaal Centrum 01:00Partial coverage0 min—
Sat 17 OctVeenendaal Centrum 00:59Partial coverage0 min—
Fri 16 Oct— 01:04+6 min+7 min
Thu 15 Oct— 00:52No data—
Wed 14 Oct— 00:520 min—
Tue 13 Oct— 00:520 min—
Mon 12 Oct— 00:520 min—
Sat 10 Oct— 00:530 min—
Fri 9 Oct— 00:520 min—
Thu 8 Oct— 00:520 min—
Wed 7 Oct— 00:520 min—
Tue 6 Oct— 00:55+2 min+3 min
Mon 5 OctUtrecht Zuilen 00:52Partial coverage0 min—
Sun 4 OctVeenendaal Centrum 00:59No data—
Sat 3 OctMaarn 00:45No data—
Sun 27 SeptVeenendaal Centrum 00:59No data—