Train NS 7373 Breukelen – Rhenen

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 19:58 from Breukelen · Sat 7 Nov

Next departure 19:58 today · Breukelen
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 13 full · 3 partial · 12 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 17 full · 3 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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 +10 min · last fix heading to — +10 min
  • Thu 29 Oct Max en route +6 min · last fix heading to — +4 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 90% · 18
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 67% W n=3
  • 50% T n=2
  • 100% F n=4
  • 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
19:58on time on time
20:03≈ on time ≈ +1 min
20:08≈ on time ≈ +1 min
20:11 / 20:14≈ on time ≈ +1 min
20:16≈ on time ≈ +2 min
20:21≈ on time ≈ +2 min
20:25≈ on time ≈ +2 min
20:31≈ on time ≈ +2 min
20:40≈ on time ≈ +3 min
20:43 / 20:45≈ on time ≈ +3 min
20:51on time +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
Fri 6 Nov— 20:530 min—
Thu 5 Nov— 20:53No data—
Wed 4 Nov— 21:04+10 min+10 min
Mon 2 Nov— 20:590 min—
Sun 1 NovVeenendaal Centrum 20:590 min—
Sat 31 OctVeenendaal Centrum 20:59Partial coverage0 min—
Fri 30 Oct— 20:52No data—
Thu 29 Oct— 20:59+4 min+6 min
Wed 28 Oct— 20:52No data—
Tue 27 Oct— 20:55No data—
Mon 26 Oct— 20:52No data—
Sun 25 OctVeenendaal Centrum 20:59No data—
Sat 24 OctVeenendaal Centrum 21:150 min—
Fri 23 Oct— 20:25+2 min+2 min
Thu 22 Oct— 20:27No data—
Wed 21 Oct— 20:290 min—
Tue 20 Oct— 20:27No data—
Mon 19 Oct— 20:53No data—
Sun 18 OctVeenendaal Centrum 20:59Partial coverage0 min—
Sat 17 OctVeenendaal Centrum 20:59No data—
Fri 16 Oct— 20:55+2 min+2 min
Thu 15 Oct— 20:55No data—
Wed 14 Oct— 20:52No data—
Tue 13 Oct— 20:530 min—
Mon 12 Oct— 20:540 min—
Sun 11 OctVeenendaal Centrum 21:02+2 min+2 min
Sat 10 OctVeenendaal Centrum 21:00Partial coverage0 min—
Fri 9 Oct— 20:56+2 min+2 min
Thu 8 Oct— 21:110 min—
Wed 7 Oct— 20:550 min+2 min