S52 16739 Murten/Morat – Kerzers

View line S52

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

✓ Today’s run finished

Today it reached Kerzers at 10:55 +1 min

  1. Murten/Morat10:43
  2. Muntelier-Löwenberg10:46
  3. Galmiz10:49
  4. Kerzers10:54

Next service: tomorrow 10:43 from Murten/Morat · Thu 19 Nov

Next departure 10:43 tomorrow · Murten/Morat
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
98%
45/46 runs under 3 min
RT coverage: 46 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

Worst days

  • Mon 16 Nov Max en route +4 min · last fix heading to Kerzers +4 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 96% · 44
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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