S52 16747 Payerne – Kerzers

View line S52

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

It has not run yet today

Last recorded run: Friday 20 November +1 min

Next service: today 12:18 from Payerne · Sat 21 Nov

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

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

  • Early 0% · 0
  • On time 100% · 41
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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