S52 16735 Murten/Morat – Kerzers

View line S52

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

✓ Today’s run finished

Today it reached Kerzers at 09:54 0 min

  1. Murten/Morat09:43
  2. Muntelier-Löwenberg09:46
  3. Galmiz09:49
  4. Kerzers09:54

Next service: tomorrow 09:43 from Murten/Morat · Wed 18 Nov

Next departure 09:43 tomorrow · Murten/Morat
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
100%
47/47 runs under 3 min
RT coverage: 47 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 2% · 1
  • On time 98% · 46
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 47 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
09:43+1 min +1 min
09:46≈ on time ≈ +1 min
09:49≈ on time ≈ +1 min
09:54on time +1 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
Tue 17 NovKerzers 09:540 min—
Mon 16 NovKerzers 09:54−1 min—
Sun 15 NovKerzers 09:540 min—
Sat 14 NovKerzers 09:54−1 min—
Fri 13 NovKerzers 09:54+1 min—
Thu 12 NovKerzers 09:54+1 min—
Wed 11 NovKerzers 09:54+1 min—
Tue 10 NovKerzers 09:54+1 min—
Mon 9 NovKerzers 09:54+1 min—
Sun 8 NovKerzers 09:54−1 min—
Sat 7 NovKerzers 09:54−1 min—
Fri 6 NovKerzers 09:54+1 min—
Thu 5 NovKerzers 09:54−1 min—
Wed 4 NovKerzers 09:54+1 min—
Tue 3 NovKerzers 09:54+1 min—
Mon 2 NovKerzers 09:54+1 min—
Sun 1 NovKerzers 09:54−1 min—
Sat 31 OctKerzers 09:550 min—
Fri 30 OctKerzers 09:550 min—
Thu 29 OctKerzers 09:55No data—
Wed 28 OctKerzers 09:550 min—
Tue 27 OctKerzers 09:57+2 min+2 min
Mon 26 OctMurten/Morat 11:010 min—
Sun 25 OctKerzers 09:55No data—
Sat 24 OctKerzers 09:55+1 min—
Fri 23 OctKerzers 09:56+1 min—
Thu 22 OctKerzers 09:57+2 min+2 min
Wed 21 OctKerzers 09:550 min—
Tue 20 OctKerzers 09:550 min—
Mon 19 OctKerzers 09:550 min—