S52 16774 Kerzers → Murten/Morat

View line S52

Kerzers 20:05 → Murten/Morat 20:14 Daily 0 h 09 min · 4 stops BLS

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 20:05 from Kerzers · Sat 21 Nov

Next departure 20:05 today · Kerzers
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
93%
43/46 runs under 3 min
RT coverage: 46 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 Murten/Morat, 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 +6 min · last fix heading to Murten/Morat +6 min
  • Thu 22 Oct Max en route +5 min · last fix heading to Murten/Morat +5 min
  • Tue 20 Oct Max en route +5 min · last fix heading to Murten/Morat +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 43
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 46 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
20:05on time +1 min
20:09≈ on time ≈ +1 min
20:11≈ on time ≈ +2 min
20:14+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
Fri 20 NovMurten/Morat 20:140 min—
Thu 19 NovMurten/Morat 20:14+1 min+1 min
Wed 18 NovMurten/Morat 20:14+1 min+1 min
Tue 17 NovMurten/Morat 20:140 min—
Mon 16 NovMurten/Morat 20:17+2 min+3 min
Sun 15 NovMurten/Morat 20:14No data—
Sat 14 NovMurten/Morat 20:140 min—
Fri 13 NovMurten/Morat 20:140 min—
Thu 12 NovMurten/Morat 20:150 min—
Wed 11 NovMurten/Morat 20:14+2 min+2 min
Tue 10 NovMurten/Morat 20:14+1 min+1 min
Mon 9 NovMurten/Morat 20:140 min—
Sun 8 NovMurten/Morat 20:140 min—
Sat 7 NovMurten/Morat 20:140 min—
Fri 6 NovMurten/Morat 20:14+1 min+1 min
Thu 5 NovMurten/Morat 20:16+1 min+1 min
Wed 4 NovMurten/Morat 20:17+2 min+2 min
Tue 3 NovMurten/Morat 20:17+1 min+1 min
Mon 2 NovMurten/Morat 20:140 min—
Sun 1 NovMurten/Morat 20:17+1 min+1 min
Sat 31 OctMurten/Morat 20:150 min—
Fri 30 OctMurten/Morat 20:17+2 min+2 min
Thu 29 OctMurten/Morat 20:150 min—
Wed 28 OctMurten/Morat 20:150 min—
Tue 27 OctMurten/Morat 20:160 min—
Mon 26 OctMurten/Morat 20:16+1 min+1 min
Sun 25 OctMurten/Morat 20:15+1 min—
Sat 24 OctMurten/Morat 20:16+1 min—
Fri 23 OctMurten/Morat 20:21+6 min+6 min
Thu 22 OctMurten/Morat 20:20+5 min+5 min