S5 15785 Neuchâtel – Kerzers

View line S5

Neuchâtel 22:04 → Kerzers 22:27 Daily 0 h 23 min · 8 stops BLS

It has not run yet today

Last recorded run: Wednesday 18 November −1 min

Next service: today 22:04 from Neuchâtel · Thu 19 Nov

Next departure 22:04 today · Neuchâtel
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 3 no data
On-time · 90 days
98%
55/56 runs under 3 min
RT coverage: 56 full · 0 partial · 3 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

  • Sat 3 Oct Max en route +5 min · last fix heading to Kerzers +5 min

Distribution · 90 days

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

  • Early 18% · 10
  • On time 80% · 45
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=8
  • 100% W n=7
  • 100% T n=8
  • 100% F n=7
  • 86% S n=7
  • 100% S n=10

Stops and timetable

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

Last 90 days, 56 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
22:04on time on time
22:07≈ on time ≈ on time
22:10≈ on time ≈ on time
22:11≈ on time ≈ on time
22:14≈ on time ≈ on time
22:18≈ on time ≈ +1 min
22:20≈ on time ≈ +1 min
22:27on 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
Wed 18 NovKerzers 22:24−1 min—
Tue 17 NovKerzers 22:240 min—
Mon 16 NovKerzers 22:27−1 min—
Sun 15 NovKerzers 22:270 min—
Sat 14 NovKerzers 22:28−1 min—
Fri 13 NovKerzers 22:280 min—
Thu 12 NovKerzers 22:28−1 min—
Wed 11 NovKerzers 22:280 min—
Tue 10 NovKerzers 22:27−1 min—
Mon 9 NovKerzers 22:28−1 min—
Sun 8 NovKerzers 22:28−1 min—
Sat 7 NovKerzers 22:29+1 min+1 min
Fri 6 NovKerzers 22:28−1 min—
Thu 5 NovKerzers 22:27−1 min—
Wed 4 NovKerzers 22:280 min—
Tue 3 NovKerzers 22:280 min—
Mon 2 NovKerzers 22:27−1 min—
Sun 1 NovKerzers 22:280 min—
Sat 31 OctKerzers 22:28No data—
Fri 30 OctKerzers 22:28No data—
Thu 29 OctKerzers 22:29+1 min+1 min
Wed 28 OctKerzers 22:28No data—
Tue 27 OctKerzers 22:280 min—
Mon 26 OctKerzers 22:280 min—
Sun 25 OctKerzers 22:29+1 min+2 min
Sat 24 OctKerzers 22:27−1 min—
Fri 23 OctKerzers 22:30+2 min+2 min
Thu 22 OctKerzers 22:26−2 min—
Wed 21 OctKerzers 22:270 min—
Tue 20 OctKerzers 22:280 min—