R56 139 Bière – Morges

View line R56

Bière 14:33 → Morges 15:04 Mon, Tue, Wed, Thu, Fri 0 h 31 min · 14 stops MBC

✓ Today’s run finished

Today it reached Morges at 15:04 −2 min

  1. Bière14:33
  2. Ballens-Froideville14:39
  3. Reverolle14:45
  4. Bussy-Chardonney14:52
  5. Vufflens-le-Château14:55
  6. Prélionne14:59
  7. Morges15:04

Next service: tomorrow 14:33 from Bière · Fri 20 Nov

Next departure 14:33 tomorrow · Bière
On-time · 30 days
67%
20/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
75%
63/84 runs under 3 min
RT coverage: 84 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Morges, in minutes. One bar per run.

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

Worst days

  • Tue 27 Oct Max en route +12 min · last fix heading to Nyon +11 min
  • Sun 27 Sept Max en route +11 min · last fix heading to Grésaley +11 min
  • Wed 18 Nov Max en route +8 min · last fix heading to Nyon +7 min
  • Tue 15 Sept Max en route +8 min · last fix heading to La Cure +7 min
  • Tue 1 Sept Max en route +7 min · last fix heading to Sugnens +7 min

Distribution · 90 days

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

  • Early 5% · 4
  • On time 70% · 59
  • 3–10 min 23% · 19
  • 10–30 min 2% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=12
  • 54% T n=13
  • 83% W n=12
  • 75% T n=12
  • 91% F n=11
  • 82% S n=11
  • 69% S n=13

Stops and timetable

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

Last 90 days, 84 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
14:33on time on time
14:37≈ on time ≈ +1 min
14:39≈ on time ≈ +1 min
14:43 / 14:44≈ on time ≈ +2 min
14:45≈ on time ≈ +2 min
14:46≈ on time ≈ +2 min
14:49≈ +1 min ≈ +3 min
14:52≈ +1 min ≈ +3 min
14:53≈ +1 min ≈ +4 min
14:55≈ +1 min ≈ +4 min
14:58≈ +1 min ≈ +4 min
14:59≈ +1 min ≈ +5 min
15:00≈ +1 min ≈ +5 min
15:04+1 min +5 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 19 NovMorges 15:03−2 min+1 min
Wed 18 NovNyon 18:49+7 min+8 min
Tue 17 NovNyon 18:44+1 min+5 min
Mon 16 NovNyon 18:44+3 min+4 min
Sun 15 NovNyon 18:44+4 min+4 min
Sat 14 NovNyon 18:49+6 min+7 min
Fri 13 NovNyon 18:44+1 min+5 min
Thu 12 NovNyon 18:44+5 min+5 min
Wed 11 NovNyon 18:44+2 min+2 min
Tue 10 NovNyon 18:47+5 min+5 min
Mon 9 NovNyon 18:44+4 min+4 min
Sun 8 NovNyon 18:44+1 min+3 min
Sat 7 NovNyon 18:420 min+2 min
Fri 6 NovNyon 18:44+1 min+9 min
Thu 5 NovNyon 18:47+4 min+4 min
Wed 4 NovNyon 18:44+2 min+2 min
Tue 3 NovNyon 18:44+2 min+2 min
Mon 2 NovNyon 18:440 min+3 min
Sun 1 NovNyon 18:440 min+2 min
Sat 31 OctNyon 18:420 min+2 min
Fri 30 OctNyon 18:45+2 min+9 min
Thu 29 OctNyon 18:430 min—
Wed 28 OctNyon 18:42−1 min+5 min
Tue 27 OctNyon 18:54+11 min+12 min
Mon 26 OctNyon 18:47+4 min+5 min
Sun 25 OctBercher 14:380 min—
Sat 24 OctBercher 14:38+2 min+2 min
Fri 23 OctMorges 15:04−1 min+2 min
Thu 22 OctMorges 15:05+2 min+5 min
Wed 21 OctMorges 15:04+2 min+2 min