Train NS 7370 Rhenen – Breukelen

Rhenen 20:08 → Breukelen 21:00 Daily 0 h 52 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 21:04 +1 min

  1. Rhenen20:08
  2. Veenendaal West20:19
  3. Maarn20:28
  4. Bunnik20:38
  5. Utrecht Centraal20:46
  6. Utrecht Zuilen20:52
  7. Breukelen21:00

Next service: tomorrow 20:08 from Rhenen · Sat 7 Nov

Next departure 20:08 tomorrow · Rhenen
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 14 full · 4 partial · 11 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 17 full · 4 partial · 33 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

  • Thu 8 Oct Max en route +17 min · last fix heading to — +17 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 100% W n=3
  • 75% T n=4
  • 100% F n=4
  • 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, 21 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:08on time on time
20:14 / 20:16≈ on time ≈ on time
20:19≈ on time ≈ +1 min
20:28≈ on time ≈ +1 min
20:34≈ on time ≈ +1 min
20:38≈ on time ≈ +1 min
20:43≈ on time ≈ +2 min
20:46 / 20:49≈ on time ≈ +2 min
20:52≈ on time ≈ +2 min
20:56≈ on time ≈ +2 min
21:00+1 min +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
Fri 6 Nov— 21:04+1 min+1 min
Thu 5 Nov— 21:020 min—
Wed 4 Nov— 21:02+1 min—
Mon 2 Nov— 20:59No data—
Sun 1 NovMaarssen 21:140 min—
Sat 31 OctMaarssen 21:11Partial coverage0 min—
Fri 30 Oct— 21:01No data—
Thu 29 Oct— 21:06+3 min+3 min
Wed 28 Oct— 21:010 min—
Tue 27 Oct— 21:02No data—
Mon 26 Oct— 20:47No data—
Sun 25 OctMaarssen 21:10No data—
Sat 24 OctKrommenie-Assendelft 22:060 min—
Fri 23 Oct— 21:02+1 min—
Thu 22 Oct— 21:02No data—
Wed 21 Oct— 21:08No data—
Tue 20 Oct— 21:04No data—
Mon 19 Oct— 21:04No data—
Sun 18 OctMaarssen 21:10Partial coverage+1 min—
Sat 17 OctMaarssen 21:11Partial coverage0 min—
Fri 16 Oct— 21:02+2 min+2 min
Thu 15 Oct— 21:080 min—
Wed 14 Oct— 21:25No data—
Tue 13 Oct— 21:12No data—
Mon 12 Oct— 21:010 min—
Sun 11 OctMaarssen 21:070 min—
Sat 10 OctMaarssen 21:10Partial coverage+1 min—
Fri 9 Oct— 21:03+1 min+1 min
Thu 8 Oct— 21:36+17 min+17 min
Wed 7 Oct— 21:02+2 min+2 min