S52 16795 Murten/Morat – Kerzers

View line S52

Murten/Morat 00:43 → Kerzers 00:54 Daily 0 h 11 min · 4 stops BLS

✓ Today’s run finished

Today it reached Kerzers at 00:57 +3 min

  1. Murten/Morat00:43
  2. Muntelier-Löwenberg00:46
  3. Galmiz00:49
  4. Kerzers00:54

Next service: tomorrow 00:43 from Murten/Morat · Sun 8 Nov

Next departure 00:43 tomorrow · Murten/Morat
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
93%
43/46 runs under 3 min
RT coverage: 46 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Kerzers, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 28 Sept Max en route +5 min · last fix heading to Galmiz +5 min
  • Sat 24 Oct Max en route +3 min · last fix heading to Kerzers +3 min
  • Sat 7 Nov Max en route +3 min · last fix heading to Kerzers +3 min

Distribution · 90 days

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

  • Early 11% · 5
  • On time 83% · 38
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
00:43+1 min +1 min
00:46≈ on time ≈ +1 min
00:49≈ on time ≈ +1 min
00:541 min early +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 NovKerzers 00:58+3 min+3 min
Fri 6 NovKerzers 00:54−1 min—
Thu 5 NovKerzers 00:54−1 min—
Wed 4 NovKerzers 00:54−1 min—
Tue 3 NovKerzers 00:540 min—
Mon 2 NovKerzers 00:54−2 min—
Sun 1 NovKerzers 00:57+2 min+2 min
Sat 31 OctKerzers 00:550 min—
Fri 30 OctKerzers 00:54−1 min—
Thu 29 OctKerzers 00:54−1 min—
Wed 28 OctKerzers 00:55−1 min—
Tue 27 OctKerzers 00:550 min—
Mon 26 OctKerzers 00:54−1 min—
Sun 25 OctKerzers 00:550 min—
Sat 24 OctKerzers 00:58+3 min+3 min
Fri 23 OctKerzers 00:56+1 min—
Thu 22 OctKerzers 00:550 min—
Wed 21 OctKerzers 00:54−1 min—
Tue 20 OctKerzers 00:57+2 min+2 min
Mon 19 OctKerzers 00:550 min—
Sun 18 OctKerzers 00:560 min—
Sat 17 OctKerzers 00:57+2 min+2 min
Fri 16 OctKerzers 00:57+2 min+2 min
Thu 15 OctKerzers 00:58+2 min+4 min
Wed 14 OctKerzers 00:56+1 min+1 min
Tue 13 OctKerzers 00:550 min—
Mon 12 OctKerzers 00:54−1 min—
Sun 11 OctKerzers 00:550 min—
Sat 10 OctKerzers 00:550 min—
Fri 9 OctKerzers 00:56+1 min—