Train NS 7395 Breukelen – Utrecht Centraal

Breukelen 01:28 → Utrecht Centraal 01:41 Daily 0 h 13 min · 4 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:43 0 min

  1. Breukelen01:28
  2. Maarssen01:33
  3. Utrecht Zuilen01:38
  4. Utrecht Centraal01:41

Next service: tomorrow 01:28 from Breukelen · Sun 8 Nov

Next departure 01:28 tomorrow · Breukelen
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 0 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 8 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 Utrecht Centraal, 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

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

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

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 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
01:28on time on time
01:33≈ on time ≈ on time
01:38≈ on time ≈ on time
01:41on time on time

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
Sat 7 Nov— 01:430 min—
Thu 5 Nov— 01:430 min—
Tue 3 Nov— 01:420 min—
Mon 2 NovMaarssen 01:490 min—
Sun 1 Nov— 01:420 min—
Thu 29 Oct— 01:420 min—
Wed 28 Oct— 01:420 min—
Tue 27 Oct— 01:420 min—
Mon 26 OctMaarssen 01:470 min—
Sun 25 Oct— 01:420 min—
Sat 24 Oct— 01:330 min—
Fri 23 Oct— 01:420 min—
Wed 21 Oct— 01:420 min—
Mon 19 OctMaarssen 01:470 min—
Sun 18 OctMaarssen 01:470 min—
Tue 13 Oct— 01:510 min—
Mon 12 OctMaarssen 01:470 min—
Fri 9 Oct— 01:420 min—
Wed 7 Oct— 01:420 min—
Tue 6 Oct— 01:420 min—
Mon 5 OctMaarssen 01:47No data—
Mon 28 SeptMaarssen 01:47No data—
Mon 21 SeptMaarssen 01:47No data—
Mon 7 SeptMaarssen 01:47No data—
Mon 31 AugMaarssen 01:47No data—
Mon 24 AugMaarssen 01:47No data—
Mon 17 AugUtrecht Zuilen 01:53No data—
Mon 10 AugMaarssen 01:47No data—