S52 16723 Payerne – Kerzers

View line S52

Payerne 06:18 → Kerzers 06:54 Daily 0 h 36 min · 9 stops BLS

✓ Today’s run finished

Today it reached Kerzers at 06:55 +1 min

  1. Payerne06:18
  2. Corcelles-Nord06:21
  3. Domdidier06:26
  4. Avenches06:30
  5. Murten/Morat06:38
  6. Galmiz06:49
  7. Kerzers06:54

Next service: tomorrow 06:18 from Payerne · Sat 7 Nov

Next departure 06:18 tomorrow · Payerne
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sat 31 Oct Max en route +4 min · last fix heading to Kerzers +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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