S52 16759 Payerne – Kerzers

View line S52

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

It has not run yet today

Last recorded run: Monday 16 November −1 min

Next service: today 15:18 from Payerne · Tue 17 Nov

Next departure 15:18 today · Payerne
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
51/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

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 98% · 50
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
15:18+1 min +1 min
15:21≈ on time ≈ +1 min
15:24≈ on time ≈ +1 min
15:27≈ on time ≈ +1 min
15:30 / 15:31≈ on time ≈ +1 min
15:38 / 15:43≈ on time ≈ +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
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—
Fri 23 OctKerzers 15:540 min—
Thu 22 OctKerzers 15:56+1 min—
Wed 21 OctKerzers 15:54−1 min—
Tue 20 OctKerzers 15:550 min—
Mon 19 OctKerzers 15:54−1 min—
Sun 18 OctKerzers 15:54−1 min—