S52 16743 Murten/Morat – Kerzers

View line S52

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

It has not run yet today

Last recorded run: Thursday 19 November No data

Next service: today 11:43 from Murten/Morat · Fri 20 Nov

Next departure 11:43 today · Murten/Morat
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 38 full · 0 partial · 12 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: 0 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

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

  • Early 3% · 1
  • On time 97% · 37
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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