R12 177 Yverdon-les-Bains – Ste-Croix

View line R12

Yverdon-les-Bains 22:35 → Ste-Croix 23:10 Daily 0 h 35 min · 9 stops Travys

Running now · updated 23:03

Position estimated from the timetable

Between Six-Fontaines and Ste-Croix 0 min

Estimated arrival at Ste-Croix 23:10 · 38 km/h

  1. Yverdon-les-Bains22:35
  2. Yverdon William Barbey22:36
  3. Valeyres-sous-Montagny22:39
  4. Essert-sous-Champvent22:42
  5. Vuiteboeuf22:47
  6. Six-Fontaines22:55
  7. Ste-Croix23:10

Today it is running no worse than usual: typical arrival delay is 0 min; 97% of the last 30 runs arrived on time.

On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
67/70 runs under 3 min
RT coverage: 70 full · 0 partial · 0 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 Ste-Croix, in minutes. One bar per run.

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

Worst days

  • Sat 5 Sept Max en route +5 min · last fix heading to Bercher +5 min
  • Fri 21 Aug Max en route +3 min · last fix heading to Ste-Croix +3 min
  • Tue 20 Oct Max en route +5 min · last fix heading to Bercher +3 min

Distribution · 90 days

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

  • Early 27% · 19
  • On time 69% · 48
  • 3–10 min 4% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 90% T n=10
  • 100% W n=10
  • 100% T n=8
  • 91% F n=11
  • 91% S n=11
  • 100% S n=10

Stops and timetable

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

Last 90 days, 70 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 10Today
22:35on time +1 minPassed
22:36≈ on time ≈ +1 minPassed
22:37≈ on time ≈ +1 minPassed
22:39≈ on time ≈ +1 minPassed
22:42≈ on time ≈ +1 minPassed
22:47≈ on time ≈ +1 minPassed
22:51≈ on time ≈ +1 minPassed
22:55≈ on time ≈ +1 minPassed
23:10on time +1 minNext

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
Mon 16 NovSte-Croix 22:590 min+1 min
Sun 15 NovBercher 00:040 min+3 min
Sat 14 NovBercher 00:09+1 min+2 min
Fri 13 NovBercher 00:07−1 min+2 min
Thu 12 NovBercher 00:05+1 min+4 min
Wed 11 NovBercher 00:070 min+8 min
Tue 10 NovBercher 00:080 min+9 min
Mon 9 NovBercher 00:050 min+2 min
Sun 8 NovBercher 00:080 min+2 min
Sat 7 NovBercher 00:040 min+2 min
Fri 6 NovBercher 00:080 min+2 min
Thu 5 NovBercher 00:040 min+4 min
Wed 4 NovBercher 00:07−1 min+4 min
Tue 3 NovBercher 00:08−1 min+2 min
Mon 2 NovBercher 00:09+1 min+3 min
Sun 1 NovBercher 00:080 min+2 min
Sat 31 OctBercher 00:080 min+2 min
Fri 30 OctBercher 00:06−1 min+1 min
Thu 29 OctBercher 00:06−1 min+2 min
Wed 28 OctBercher 00:06−1 min+3 min
Tue 27 OctBercher 00:07−1 min+4 min
Mon 26 OctBercher 00:07−1 min+5 min
Sun 25 OctBercher 00:070 min+4 min
Sat 24 OctBercher 00:080 min+12 min
Fri 23 OctBercher 00:07−1 min+6 min
Thu 22 OctBercher 00:080 min+2 min
Wed 21 OctBercher 00:06−1 min+2 min
Tue 20 OctBercher 00:08+3 min+5 min
Mon 19 OctBercher 00:06−1 min+3 min
Sun 18 OctBercher 00:080 min+2 min