S52 16719 Murten/Morat – Kerzers

View line S52

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

✓ Today’s run finished

Today it reached Kerzers at 05:54 −1 min

  1. Murten/Morat05:43
  2. Muntelier-Löwenberg05:46
  3. Galmiz05:49
  4. Kerzers05:54

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

Next departure 05:43 tomorrow · Murten/Morat
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 0 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

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

  • Early 5% · 2
  • On time 95% · 37
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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