Train NS 7377 Breukelen – Rhenen

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

✓ Today’s run finished

Today, last fix heading to — at 21:53 0 min

  1. Breukelen20:58
  2. Utrecht Zuilen21:08
  3. Utrecht Centraal21:11
  4. Bunnik21:21
  5. Maarn21:31
  6. Veenendaal West21:40
  7. Rhenen21:51

Next service: tomorrow 20:58 from Breukelen · Fri 6 Nov

Next departure 20:58 tomorrow · Breukelen
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 15 full · 3 partial · 10 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 17 full · 3 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Wed 4 Nov Max en route +7 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 67% W n=3
  • 100% T n=4
  • 100% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 20 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:58on time on time
21:03≈ on time ≈ on time
21:08≈ on time ≈ on time
21:11 / 21:14≈ on time ≈ on time
21:16≈ on time ≈ on time
21:21≈ on time ≈ on time
21:25≈ on time ≈ on time
21:31≈ on time ≈ on time
21:40≈ on time ≈ on time
21:43 / 21:45≈ on time ≈ on time
21: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
Thu 5 Nov— 21:530 min—
Wed 4 Nov— 22:03+5 min+7 min
Mon 2 Nov— 21:24+1 min—
Sun 1 NovVeenendaal Centrum 21:590 min—
Sat 31 OctVeenendaal Centrum 22:00Partial coverage0 min—
Thu 29 Oct— 21:520 min—
Wed 28 Oct— 21:52No data—
Tue 27 Oct— 21:53No data—
Mon 26 Oct— 21:56No data—
Sun 25 OctVeenendaal Centrum 22:00No data—
Sat 24 OctVeenendaal Centrum 22:150 min—
Fri 23 Oct— 21:240 min—
Thu 22 Oct— 21:330 min—
Wed 21 Oct— 21:260 min—
Tue 20 Oct— 21:27No data—
Mon 19 Oct— 21:53No data—
Sun 18 OctVeenendaal Centrum 22:00Partial coverage+2 min+2 min
Sat 17 OctVeenendaal Centrum 21:59No data—
Fri 16 Oct— 21:540 min+1 min
Thu 15 Oct— 21:54No data—
Wed 14 Oct— 21:52No data—
Tue 13 Oct— 21:53No data—
Mon 12 Oct— 21:520 min—
Sun 11 OctVeenendaal Centrum 22:130 min—
Sat 10 OctVeenendaal Centrum 21:59Partial coverage0 min—
Fri 9 Oct— 21:530 min—
Thu 8 Oct— 21:520 min—
Wed 7 Oct— 21:520 min—
Tue 6 Oct— 21:520 min—
Mon 5 Oct— 21:520 min—