R9 24924 Murten/Morat – Allaman

View line R9

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

✓ Today’s run finished

Today it reached Allaman at 11:27 0 min

  1. Murten/Morat09:38
  2. Dompierre FR09:50
  3. Henniez10:11
  4. Châtillens10:33
  5. Puidoux10:51
  6. Morges-St-Jean11:15
  7. Allaman11:27

Next service: tomorrow 09:38 from Murten/Morat · Tue 10 Nov

Next departure 09:38 tomorrow · Murten/Morat
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
98%
50/51 runs under 3 min
RT coverage: 51 full · 0 partial · 2 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 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

  • Mon 5 Oct Max en route +21 min · last fix heading to Allaman +21 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 94% · 48
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=6
  • 100% W n=7
  • 100% T n=7
  • 100% F n=8
  • 100% S n=7
  • 100% S n=9

Stops and timetable

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

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