Train NS 7368 Rhenen – Breukelen

Rhenen 19:38 → Breukelen 20:30 Daily 0 h 52 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 20:54 +2 min

  1. Rhenen19:38
  2. Veenendaal West19:49
  3. Maarn19:58
  4. Bunnik20:08
  5. Utrecht Centraal20:16
  6. Utrecht Zuilen20:22
  7. Breukelen20:30

Next service: tomorrow 19:38 from Rhenen · Thu 12 Nov

Next departure 19:38 tomorrow · Rhenen
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 12 full · 4 partial · 13 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 19 full · 5 partial · 32 no data
Typical delay
+1min
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

  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
19:38on time on time
19:44 / 19:46≈ on time ≈ on time
19:49≈ on time ≈ +1 min
19:58≈ on time ≈ +1 min
20:04≈ on time ≈ +1 min
20:08≈ on time ≈ +1 min
20:13≈ on time ≈ +1 min
20:16 / 20:19≈ on time ≈ +1 min
20:22≈ on time ≈ +1 min
20:26≈ on time ≈ +2 min
20:30on time +2 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
Wed 11 Nov— 20:54+2 min+2 min
Tue 10 Nov— 20:320 min—
Mon 9 Nov— 20:290 min—
Sun 8 NovMaarssen 20:39Partial coverage+1 min+1 min
Sat 7 NovMaarssen 20:39Partial coverage+1 min—
Fri 6 Nov— 20:300 min—
Thu 5 Nov— 20:300 min—
Wed 4 Nov— 20:34+2 min+2 min
Mon 2 Nov— 20:19No data—
Sun 1 NovMaarssen 20:380 min—
Sat 31 OctMaarssen 20:40Partial coverage0 min—
Fri 30 Oct— 20:31No data—
Thu 29 Oct— 20:32+1 min+1 min
Wed 28 Oct— 20:33No data—
Tue 27 Oct— 20:36No data—
Mon 26 OctVeenendaal West 20:32No data—
Sun 25 OctMaarssen 20:40No data—
Sat 24 OctKrommenie-Assendelft 21:360 min—
Fri 23 Oct— 20:37+5 min+5 min
Thu 22 Oct— 20:32No data—
Wed 21 Oct— 20:550 min—
Tue 20 Oct— 20:340 min—
Mon 19 Oct— 20:32No data—
Sun 18 OctMaarssen 20:41Partial coverage+2 min+2 min
Sat 17 OctMaarssen 20:41No data—
Fri 16 OctVeenendaal West 20:34No data—
Thu 15 Oct— 20:34No data—
Wed 14 OctVeenendaal Centrum 20:34No data—
Tue 13 Oct— 20:34No data—
Mon 12 Oct— 20:320 min—