R9 24982 Murten/Morat – Allaman

View line R9

Murten/Morat 21:38 → Allaman 23:30 Daily 1 h 52 min · 25 stops SBB CFF FFS

It has not run yet today

Last recorded run: Monday 16 November 0 min

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

Next departure 21:38 today · Murten/Morat
On-time · 30 days
79%
23/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
88%
66/75 runs under 3 min
RT coverage: 75 full · 0 partial · 3 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +7 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 +29 min · last fix heading to Allaman +29 min
  • Tue 10 Nov Max en route +16 min · last fix heading to Allaman +15 min
  • Sat 24 Oct Max en route +12 min · last fix heading to Allaman +12 min
  • Wed 14 Oct Max en route +6 min · last fix heading to Allaman +6 min
  • Sat 31 Oct Max en route +6 min · last fix heading to Allaman +6 min

Distribution · 90 days

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

  • Early 3% · 2
  • On time 85% · 64
  • 3–10 min 8% · 6
  • 10–30 min 4% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 91% T n=11
  • 82% W n=11
  • 100% T n=12
  • 90% F n=10
  • 73% S n=11
  • 82% S n=11

Stops and timetable

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

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