Train NS 7385 Breukelen – Rhenen

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

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 22:58 from Breukelen · Wed 11 Nov

Next departure 22:58 today · Breukelen
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 13 full · 3 partial · 10 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 21 full · 3 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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 +4 min · last fix heading to — +4 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
  • 67% W n=3
  • 100% T n=3
  • 100% F n=4
  • 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
22:58on time on time
23:03≈ on time ≈ on time
23:08≈ on time ≈ on time
23:11 / 23:14≈ on time ≈ on time
23:16≈ on time ≈ on time
23:21≈ on time ≈ on time
23:25≈ on time ≈ on time
23:31≈ on time ≈ on time
23:40≈ on time ≈ on time
23:43 / 23:45≈ on time ≈ on time
23:51on time +1 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
Tue 10 Nov— 23:520 min—
Mon 9 Nov— 23:530 min—
Sun 8 NovVeenendaal Centrum 23:59Partial coverage0 min—
Sat 7 NovBunnik 23:530 min—
Fri 6 Nov— 23:530 min+2 min
Thu 5 Nov— 23:540 min—
Wed 4 Nov— 23:59+4 min+4 min
Sun 1 NovVeenendaal Centrum 23:590 min—
Sat 31 OctBunnik 23:54Partial coverage0 min—
Fri 30 Oct— 23:52No data—
Wed 28 Oct— 23:54No data—
Tue 27 Oct— 23:530 min—
Mon 26 Oct— 23:52No data—
Sun 25 OctVeenendaal Centrum 23:59No data—
Sat 24 OctAmsterdam Centraal 00:090 min—
Fri 23 Oct— 23:110 min—
Thu 22 Oct— 23:26No data—
Wed 21 Oct— 23:27No data—
Tue 20 Oct— 23:26No data—
Mon 19 Oct— 23:53No data—
Sun 18 OctVeenendaal Centrum 23:59Partial coverage0 min—
Sat 17 OctVeenendaal Centrum 23:59No data—
Fri 16 Oct— 23:52+1 min—
Thu 15 Oct— 00:070 min—
Wed 14 Oct— 23:520 min—
Tue 13 Oct— 23:57No data—
Mon 12 Oct— 23:520 min—
Sun 11 OctVeenendaal Centrum 00:010 min—
Sat 10 Oct— 23:530 min—
Fri 9 Oct— 23:520 min—