S35 6530 Lyss – Kerzers

View line S35

Lyss 17:35 → Kerzers 17:55 Daily 0 h 20 min · 8 stops BLS

Running now · updated 17:43

Position estimated from the timetable

Between Bargen BE and Kallnach 0 min

Estimated arrival at Kerzers 17:55 · 49 km/h

  1. Lyss17:35
  2. Lyss Grien17:37
  3. Aarberg17:41
  4. Bargen BE17:43
  5. Kallnach17:46
  6. Fräschels17:50
  7. Kerzers17:55

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 30 runs arrived on time.

On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
100%
44/44 runs under 3 min
RT coverage: 43 full · 1 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 44 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 10Today
17:35on time on timePassed
17:37≈ on time ≈ on timePassed
17:41≈ on time ≈ on timePassed
17:43≈ on time ≈ on timePassed
17:46≈ on time ≈ +1 minNext
17:50≈ on time ≈ +1 min
17:52≈ on time ≈ +1 min
17:55on 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 NovAarberg 17:39Partial coverage0 min—
Sun 15 NovKerzers 17:57+1 min—
Sat 14 NovKerzers 17:540 min—
Fri 13 NovKerzers 17:58+1 min+1 min
Thu 12 NovKerzers 17:540 min—
Wed 11 NovKerzers 17:540 min—
Tue 10 NovKerzers 17:540 min—
Mon 9 NovKerzers 17:540 min—
Sun 8 NovKerzers 17:540 min—
Sat 7 NovKerzers 17:540 min—
Fri 6 NovKerzers 17:540 min—
Thu 5 NovKerzers 17:540 min—
Wed 4 NovKerzers 17:57+1 min+1 min
Tue 3 NovKerzers 17:540 min—
Mon 2 NovKerzers 17:58+2 min+2 min
Sun 1 NovKerzers 17:550 min—
Sat 31 OctKerzers 17:56+1 min—
Fri 30 OctKerzers 17:560 min—
Thu 29 OctKerzers 17:58+2 min+2 min
Wed 28 OctKerzers 17:57+1 min—
Tue 27 OctKerzers 17:560 min—
Mon 26 OctKerzers 17:570 min—
Sun 25 OctKerzers 17:55−1 min—
Sat 24 OctKerzers 17:560 min—
Fri 23 OctKerzers 17:57+1 min—
Thu 22 OctKerzers 17:560 min—
Wed 21 OctKerzers 17:58+2 min+2 min
Tue 20 OctKerzers 17:560 min—
Mon 19 OctKerzers 17:57+1 min—
Sun 18 OctKerzers 17:55−1 min—