S52 16771 Murten/Morat → Kerzers

View line S52

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

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

✓ Today’s run finished

Today it reached Kerzers at 18:57 +3 min

  1. Murten/Morat18:43
  2. Muntelier-Löwenberg18:46
  3. Galmiz18:49
  4. Kerzers18:54

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

Next departure 18:43 tomorrow · Murten/Morat
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
96%
49/51 runs under 3 min
RT coverage: 51 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 22 Oct Max en route +26 min · last fix heading to Kerzers +26 min
  • Tue 3 Nov Max en route +7 min · last fix heading to Kerzers +7 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 94% · 48
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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