Train NS 7387 Breukelen – Rhenen

Breukelen 23:28 → Rhenen 00:21 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 23:28 from Breukelen · Sat 7 Nov

Next departure 23:28 today · Breukelen
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 20 full · 4 partial · 3 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 23 full · 5 partial · 13 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: +2 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

  • Sun 11 Oct Max en route +5 min · last fix heading to Veenendaal Centrum +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
23:28on time on time
23:33≈ on time ≈ on time
23:38≈ on time ≈ on time
23:41 / 23:44≈ on time ≈ on time
23:46≈ on time ≈ +1 min
23:51≈ on time ≈ +1 min
23:55≈ on time ≈ +1 min
00:01≈ on time ≈ +1 min
00:10≈ on time ≈ +1 min
00:13 / 00:15≈ on time ≈ +2 min
00:21on 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
Fri 6 Nov— 00:230 min+1 min
Thu 5 Nov— 00:290 min—
Wed 4 Nov— 00:230 min+2 min
Mon 2 Nov— 00:24+3 min+3 min
Sun 1 NovVeenendaal Centrum 00:29Partial coverage0 min—
Fri 30 Oct— 00:220 min—
Thu 29 Oct— 00:25+2 min+2 min
Wed 28 Oct— 00:220 min—
Tue 27 Oct— 00:220 min—
Mon 26 Oct— 00:220 min—
Sun 25 OctVeenendaal Centrum 00:29Partial coverage0 min—
Sat 24 OctKrommenie-Assendelft 00:380 min—
Fri 23 Oct— 23:460 min—
Thu 22 Oct— 23:59No data—
Wed 21 Oct— 23:57No data—
Tue 20 Oct— 23:56No data—
Mon 19 Oct— 00:230 min—
Sun 18 OctVeenendaal Centrum 00:29Partial coverage0 min—
Sat 17 OctVeenendaal Centrum 00:30Partial coverage0 min—
Fri 16 Oct— 00:220 min+2 min
Thu 15 Oct— 00:230 min—
Wed 14 Oct— 00:220 min—
Tue 13 Oct— 00:230 min—
Mon 12 Oct— 00:23+1 min—
Sun 11 OctVeenendaal Centrum 00:35+4 min+5 min
Sat 10 Oct— 00:230 min—
Fri 9 Oct— 00:230 min—
Thu 8 Oct— 00:250 min+1 min
Wed 7 Oct— 00:230 min+1 min
Tue 6 Oct— 00:220 min—