R9 24908 Murten/Morat – Allaman

View line R9

Murten/Morat 05:38 → Allaman 07:27 Daily 1 h 49 min · 24 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Allaman at 07:29 +2 min

  1. Murten/Morat05:38
  2. Dompierre FR05:50
  3. Henniez06:11
  4. Châtillens06:33
  5. Puidoux06:51
  6. Morges-St-Jean07:15
  7. Allaman07:27

Next service: tomorrow 05:38 from Murten/Morat · Wed 18 Nov

Next departure 05:38 tomorrow · Murten/Morat
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
95%
57/60 runs under 3 min
RT coverage: 60 full · 0 partial · 2 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

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

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

Worst days

  • Wed 4 Nov Max en route +14 min · last fix heading to Allaman +14 min
  • Mon 28 Sept Max en route +4 min · last fix heading to Allaman +4 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Allaman +3 min

Distribution · 90 days

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

  • Early 3% · 2
  • On time 92% · 55
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 100% T n=10
  • 89% W n=9
  • 88% T n=8
  • 100% F n=8
  • 100% S n=8
  • 100% S n=9

Stops and timetable

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

Last 90 days, 60 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
05:38on time on time
05:41≈ on time ≈ on time
05:45≈ on time ≈ +1 min
05:48≈ on time ≈ +1 min
05:50≈ on time ≈ +1 min
05:53≈ on time ≈ +1 min
05:57 / 06:02≈ on time ≈ +1 min
06:08≈ on time ≈ +1 min
06:11≈ on time ≈ +1 min
06:15≈ on time ≈ +1 min
06:20≈ on time ≈ +1 min
06:28 / 06:29≈ on time ≈ +1 min
06:33 / 06:34≈ on time ≈ +1 min
06:37≈ on time ≈ +1 min
06:42 / 06:44≈ on time ≈ +1 min
06:51≈ on time ≈ +1 min
07:02 / 07:04≈ on time ≈ +2 min
07:09≈ on time ≈ +2 min
07:14≈ on time ≈ +2 min
07:15≈ on time ≈ +2 min
07:18≈ +1 min ≈ +2 min
07:21≈ +1 min ≈ +2 min
07:23≈ +1 min ≈ +2 min
07:27+1 min +2 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
Tue 17 NovAllaman 07:29+2 min+2 min
Mon 16 NovAllaman 07:29+1 min+1 min
Sun 15 NovAllaman 07:280 min—
Sat 14 NovAllaman 07:29+2 min+2 min
Fri 13 NovAllaman 07:290 min—
Thu 12 NovAllaman 07:30+1 min+1 min
Wed 11 NovAllaman 07:29+1 min—
Tue 10 NovAllaman 07:29+1 min+1 min
Mon 9 NovAllaman 07:29+1 min+1 min
Sun 8 NovAllaman 07:290 min—
Sat 7 NovAllaman 07:27−1 min—
Fri 6 NovAllaman 07:27−1 min—
Thu 5 NovAllaman 07:280 min—
Wed 4 NovAllaman 07:42+14 min+14 min
Tue 3 NovAllaman 07:29+1 min—
Mon 2 NovAllaman 07:29+2 min+2 min
Sun 1 NovAllaman 07:27−1 min—
Sat 31 OctAllaman 07:27−1 min—
Fri 30 OctAllaman 07:280 min—
Thu 29 OctAllaman 07:27−1 min—
Wed 28 OctAllaman 07:28−1 min—
Tue 27 OctAllaman 07:290 min—
Mon 26 OctAllaman 07:28−1 min—
Sun 25 OctAllaman 07:280 min—
Sat 24 OctAllaman 07:29+2 min+2 min
Fri 23 OctAllaman 07:30+2 min+2 min
Thu 22 OctAllaman 07:280 min—
Wed 21 OctAllaman 07:30+2 min+2 min
Tue 20 OctAllaman 07:30+1 min—
Mon 19 OctAllaman 07:29+1 min+1 min