S52 16790 Kerzers – Murten/Morat

View line S52

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

✓ Today’s run finished

Today it reached Murten/Morat at 00:15 +1 min

  1. Kerzers00:05
  2. Galmiz00:09
  3. Muntelier-Löwenberg00:11
  4. Murten/Morat00:14

Next service: tomorrow 00:05 from Kerzers · Sun 8 Nov

Next departure 00:05 tomorrow · Kerzers
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
92%
34/37 runs under 3 min
RT coverage: 37 full · 0 partial · 0 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

  • Wed 7 Oct Max en route +3 min · last fix heading to Murten/Morat +3 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Murten/Morat +3 min
  • Sat 24 Oct Max en route +3 min · last fix heading to Murten/Morat +3 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 89% · 33
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 60% W n=5
  • 100% T n=5
  • 100% F n=6
  • 80% S n=5
  • 100% S n=5

Stops and timetable

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

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