Train NS 7374 Rhenen – Breukelen

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 21:08 from Rhenen · Fri 6 Nov

Next departure 21:08 today · Rhenen
On-time · 30 days
85%
11/13 runs under 3 min
RT coverage: 10 full · 3 partial · 15 no data
On-time · 90 days
88%
14/16 runs under 3 min
RT coverage: 13 full · 3 partial · 32 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Wed 4 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 9 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 14
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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