S52 16759 Murten/Morat → Kerzers

View line S52

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

S52 16759 Murten/Morat–Kerzers: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 16:32 (GMT+1).

✓ Today’s run finished

Today it reached Kerzers at 15:55 +1 min

  1. Murten/Morat15:43
  2. Muntelier-Löwenberg15:46
  3. Galmiz15:49
  4. Kerzers15:54

Next service: tomorrow 15:43 from Murten/Morat · Mon 23 Nov

Next departure 15:43 tomorrow · Murten/Morat
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
56/57 runs under 3 min
RT coverage: 57 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

Worst days

  • Thu 19 Nov Max en route +4 min · last fix heading to Kerzers +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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