Train NS 7369 Breukelen – Rhenen

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

✓ Today’s run finished

Today, last fix heading to — at 19:52 0 min

  1. Breukelen18:58
  2. Utrecht Zuilen19:08
  3. Utrecht Centraal19:11
  4. Bunnik19:21
  5. Maarn19:31
  6. Veenendaal West19:40
  7. Rhenen19:51

Next service: tomorrow 18:58 from Breukelen · Sat 7 Nov

Next departure 18:58 tomorrow · Breukelen
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 14 full · 5 partial · 9 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 17 full · 5 partial · 38 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 +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 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
  • 75% W n=4
  • 100% T n=4
  • 100% F n=3
  • 100% 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, 22 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
18:58on time on time
19:03≈ on time ≈ on time
19:08≈ on time ≈ on time
19:11 / 19:14≈ on time ≈ on time
19:16≈ on time ≈ on time
19:21≈ on time ≈ on time
19:25≈ on time ≈ +1 min
19:31≈ on time ≈ +1 min
19:40≈ on time ≈ +1 min
19:43 / 19:45≈ on time ≈ +1 min
19: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
Fri 6 Nov— 19:520 min—
Thu 5 Nov— 19:520 min—
Wed 4 Nov— 20:04+8 min+8 min
Mon 2 Nov— 19:52No data—
Sun 1 NovVeenendaal Centrum 19:590 min—
Sat 31 OctVeenendaal Centrum 19:59Partial coverage0 min—
Thu 29 Oct— 19:53+1 min—
Wed 28 Oct— 19:520 min—
Tue 27 Oct— 19:53No data—
Mon 26 OctVeenendaal Centrum 19:52No data—
Sun 25 OctVeenendaal Centrum 19:59No data—
Sat 24 OctVeenendaal Centrum 20:150 min—
Fri 23 OctBunnik 19:360 min—
Thu 22 Oct— 19:27No data—
Wed 21 Oct— 19:27No data—
Tue 20 Oct— 19:27No data—
Mon 19 Oct— 19:530 min—
Sun 18 OctVeenendaal Centrum 19:59Partial coverage+1 min—
Sat 17 OctVeenendaal Centrum 20:06Partial coverage0 min—
Fri 16 OctVeenendaal Centrum 19:59No data—
Thu 15 Oct— 19:540 min—
Wed 14 OctVeenendaal Centrum 19:59Partial coverage0 min—
Tue 13 Oct— 19:53No data—
Mon 12 Oct— 19:530 min—
Sun 11 OctVeenendaal Centrum 20:010 min—
Sat 10 OctVeenendaal Centrum 19:59Partial coverage0 min—
Fri 9 Oct— 19:530 min—
Thu 8 Oct— 19:520 min—
Wed 7 Oct— 19:57+2 min+3 min
Tue 6 Oct— 19:520 min—