R9 24968 Murten/Morat – Allaman

View line R9

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

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 18:38 from Murten/Morat · Sat 14 Nov

Next departure 18:38 today · Murten/Morat
On-time · 30 days
86%
25/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
88%
51/58 runs under 3 min
RT coverage: 58 full · 0 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Fri 23 Oct Max en route +13 min · last fix heading to Allaman +13 min
  • Sun 18 Oct Max en route +10 min · last fix heading to Allaman +10 min
  • Tue 3 Nov Max en route +10 min · last fix heading to Allaman +10 min
  • Thu 8 Oct Max en route +6 min · last fix heading to Allaman +6 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Allaman +5 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 86% · 50
  • 3–10 min 7% · 4
  • 10–30 min 5% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 75% T n=8
  • 88% W n=8
  • 86% T n=7
  • 85% F n=13
  • 100% S n=7
  • 86% S n=7

Stops and timetable

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

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