Train NS 7383 Breukelen – Rhenen

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 22:28 from Breukelen · Fri 6 Nov

Next departure 22:28 today · Breukelen
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 14 full · 2 partial · 11 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 17 full · 2 partial · 28 no data
Typical delay
0min
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 Rhenen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 100% 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, 19 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:28on time on time
22:33≈ on time ≈ on time
22:38≈ on time ≈ on time
22:41 / 22:44≈ on time ≈ +1 min
22:46≈ on time ≈ +1 min
22:51≈ on time ≈ +1 min
22:55≈ on time ≈ +1 min
23:01≈ on time ≈ +1 min
23:10≈ on time ≈ +2 min
23:13 / 23:15≈ on time ≈ +2 min
23: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
Thu 5 Nov— 23:23No data—
Wed 4 Nov— 23:230 min—
Mon 2 Nov— 23:24+2 min+2 min
Sun 1 NovVeenendaal Centrum 23:290 min—
Sat 31 OctVeenendaal Centrum 23:29Partial coverage0 min—
Thu 29 Oct— 23:220 min—
Wed 28 Oct— 23:27No data—
Tue 27 Oct— 23:23No data—
Mon 26 Oct— 23:22No data—
Sun 25 OctVeenendaal Centrum 23:29No data—
Sat 24 OctBreukelen 23:390 min—
Fri 23 Oct— 22:470 min—
Thu 22 Oct— 22:57No data—
Wed 21 Oct— 23:03No data—
Tue 20 Oct— 22:57No data—
Mon 19 Oct— 23:37No data—
Sun 18 OctVeenendaal Centrum 23:29Partial coverage0 min—
Sat 17 OctVeenendaal Centrum 23:29No data—
Fri 16 Oct— 23:27+3 min+3 min
Thu 15 Oct— 23:24No data—
Wed 14 Oct— 23:220 min—
Tue 13 Oct— 23:220 min—
Mon 12 Oct— 23:230 min—
Sun 11 OctVeenendaal Centrum 23:33+2 min+4 min
Sat 10 Oct— 23:230 min—
Fri 9 Oct— 23:27+2 min+2 min
Thu 8 Oct— 23:220 min—
Wed 7 Oct— 23:25+2 min+2 min
Tue 6 Oct— 23:220 min—
Mon 5 Oct— 23:220 min—