R22 57 Yverdon-les-Bains – Ste-Croix

View line R22

Yverdon-les-Bains 17:33 → Ste-Croix 18:06 Mon, Tue, Wed, Thu, Fri 0 h 33 min · 5 stops Travys

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 17:33 from Yverdon-les-Bains · Fri 6 Nov

Next departure 17:33 today · Yverdon-les-Bains
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
93%
41/44 runs under 3 min
RT coverage: 44 full · 0 partial · 4 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

  • Fri 14 Aug Max en route +11 min · last fix heading to Ste-Croix +11 min
  • Tue 25 Aug Max en route +8 min · last fix heading to Ste-Croix +7 min
  • Fri 16 Oct Max en route +4 min · last fix heading to Ste-Croix +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 91% · 40
  • 3–10 min 5% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 86% T n=7
  • 100% W n=8
  • 100% T n=7
  • 71% F n=7
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 44 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
17:33on time on time
17:43≈ on time ≈ on time
17:47≈ on time ≈ +1 min
17:51≈ on time ≈ +1 min
18:06on 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
Thu 5 NovSte-Croix 18:070 min+3 min
Wed 4 NovSte-Croix 18:070 min+2 min
Tue 3 NovSte-Croix 18:070 min+2 min
Mon 2 NovSte-Croix 18:07+1 min+3 min
Sun 1 NovAigle 17:510 min+1 min
Sat 31 OctAigle 17:51−1 min+2 min
Fri 30 OctSte-Croix 18:08+1 min+3 min
Thu 29 OctSte-Croix 18:070 min+2 min
Wed 28 OctSte-Croix 18:070 min+3 min
Tue 27 OctSte-Croix 18:070 min+3 min
Mon 26 OctSte-Croix 18:070 min+2 min
Sun 25 OctAigle 17:51−1 min+1 min
Sat 24 OctAigle 17:510 min+2 min
Fri 23 OctSte-Croix 18:070 min+1 min
Thu 22 OctSte-Croix 18:070 min+2 min
Wed 21 OctSte-Croix 18:070 min+3 min
Tue 20 OctSte-Croix 18:070 min+2 min
Mon 19 OctSte-Croix 18:070 min+4 min
Sun 18 OctAigle 17:530 min+1 min
Sat 17 OctAigle 17:510 min+1 min
Fri 16 OctSte-Croix 18:11+3 min+4 min
Thu 15 OctSte-Croix 18:08+1 min+9 min
Wed 14 OctSte-Croix 18:070 min+5 min
Tue 13 OctSte-Croix 18:070 min+6 min
Mon 12 OctSte-Croix 18:070 min+4 min
Sun 11 OctAigle 17:520 min—
Sat 10 OctAigle 17:51−1 min+2 min
Fri 9 OctSte-Croix 18:080 min+3 min
Thu 8 OctSte-Croix 18:07+1 min+5 min
Wed 7 OctSte-Croix 18:080 min+10 min