Train NS 7391 Breukelen – Utrecht Centraal

Breukelen 00:30 → Utrecht Centraal 00:42 Daily 0 h 12 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 00:42 0 min

  1. Breukelen00:30
  2. Maarssen00:34
  3. Utrecht Zuilen00:39
  4. Utrecht Centraal00:42

Next service: tomorrow 00:30 from Breukelen · Mon 9 Nov

Next departure 00:30 tomorrow · Breukelen
On-time · 30 days
92%
23/25 runs under 3 min
RT coverage: 25 full · 0 partial · 3 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 12 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: +1 min

Last 30 days

Arrival delay at Utrecht Centraal, in minutes. One bar per run.

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

Worst days

  • Thu 5 Nov Max en route +9 min · last fix heading to — +9 min
  • Mon 2 Nov Max en route +4 min · last fix heading to Utrecht Zuilen +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 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 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
00:30on time on time
00:34≈ on time ≈ on time
00:39≈ on time ≈ +1 min
00:42on 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
Sun 8 Nov— 00:420 min—
Sat 7 Nov— 00:44+1 min+1 min
Fri 6 Nov— 00:53No data—
Thu 5 Nov— 00:59+9 min+9 min
Tue 3 Nov— 00:420 min—
Mon 2 NovUtrecht Zuilen 00:59+4 min+4 min
Sun 1 Nov— 00:490 min—
Sat 31 Oct— 00:45No data—
Fri 30 Oct— 00:420 min—
Thu 29 Oct— 00:420 min—
Wed 28 Oct— 00:430 min—
Tue 27 Oct— 00:420 min—
Mon 26 OctUtrecht Zuilen 00:52No data—
Sat 24 Oct— 00:430 min—
Fri 23 Oct— 00:420 min—
Thu 22 Oct— 07:250 min—
Wed 21 Oct— 00:320 min—
Tue 20 Oct— 00:570 min—
Mon 19 OctUtrecht Zuilen 00:530 min—
Sun 18 OctUtrecht Zuilen 00:520 min—
Sat 17 Oct— 00:420 min—
Fri 16 Oct— 00:420 min—
Thu 15 Oct— 00:420 min—
Wed 14 Oct— 00:420 min—
Tue 13 Oct— 00:420 min—
Mon 12 OctUtrecht Zuilen 00:570 min—
Sun 11 Oct— 00:430 min—
Sat 10 Oct— 00:45+1 min—
Thu 8 Oct— 00:45+2 min+2 min
Wed 7 Oct— 00:420 min—