R9 24958 Murten/Morat – Allaman

View line R9

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

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 16:38 from Murten/Morat · Tue 17 Nov

Next departure 16: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
83%
54/65 runs under 3 min
RT coverage: 65 full · 0 partial · 4 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: +3 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 28 Aug Max en route +6 min · last fix heading to St-Prex +6 min
  • Tue 15 Sept Max en route +5 min · last fix heading to Etoy +5 min
  • Fri 13 Nov Max en route +4 min · last fix heading to Allaman +4 min
  • Thu 29 Oct Max en route +4 min · last fix heading to Allaman +4 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Allaman +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 54
  • 3–10 min 17% · 11
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=10
  • 78% T n=9
  • 90% W n=10
  • 67% T n=9
  • 75% F n=12
  • 100% S n=7
  • 100% S n=8

Stops and timetable

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

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