S5 15753 Neuchâtel → Kerzers

View line S5

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

S5 15753 Neuchâtel–Kerzers: final delay under 3 min on 22 of its 22 runs with data in the last 30 days (100%). Median final delay: −1 min. TrainsRadar data as of 22 Nov 2026, 16:40 (GMT+1).

✓ Today’s run finished

Today it reached Kerzers at 14:27 −1 min

  1. Neuchâtel14:04
  2. St-Blaise-Lac14:07
  3. Marin-Epagnier14:10
  4. Gampelen14:14
  5. Ins14:18
  6. Müntschemier14:20
  7. Kerzers14:27

Next service: tomorrow 14:04 from Neuchâtel · Mon 23 Nov

Next departure 14:04 tomorrow · Neuchâtel
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
100%
48/48 runs under 3 min
RT coverage: 48 full · 0 partial · 12 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 42% · 20
  • On time 58% · 28
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=10
  • 100% W n=7
  • 100% T n=1
  • 100% F n=7
  • 100% S n=9
  • 100% S n=11

Stops and timetable

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

Last 90 days, 48 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
14:04on time on time
14:07≈ on time ≈ on time
14:10≈ on time ≈ on time
14:11≈ on time ≈ on time
14:14≈ on time ≈ on time
14:18≈ 1 min early ≈ on time
14:20≈ 1 min early ≈ on time
14:271 min early on time

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
Sun 22 NovKerzers 14:27−1 min—
Sat 21 NovKerzers 14:24−1 min—
Fri 20 NovKerzers 14:28+1 min—
Thu 19 NovKerzers 14:28No data—
Wed 18 NovKerzers 14:280 min—
Tue 17 NovKerzers 14:28−1 min—
Mon 16 NovKerzers 14:28No data—
Sun 15 NovKerzers 14:24−1 min—
Sat 14 NovKerzers 14:27−1 min—
Fri 13 NovKerzers 14:280 min—
Thu 12 NovKerzers 14:28No data—
Wed 11 NovKerzers 14:27−1 min—
Tue 10 NovKerzers 14:27−1 min—
Mon 9 NovKerzers 14:28No data—
Sun 8 NovKerzers 14:27−1 min—
Sat 7 NovKerzers 14:24−1 min—
Fri 6 NovKerzers 14:29+1 min+1 min
Thu 5 NovKerzers 14:28No data—
Wed 4 NovKerzers 14:280 min—
Tue 3 NovKerzers 14:28−1 min—
Mon 2 NovKerzers 14:28No data—
Sun 1 NovKerzers 14:26−1 min—
Sat 31 OctKerzers 14:27−1 min—
Fri 30 OctKerzers 14:280 min—
Thu 29 OctKerzers 14:28No data—
Wed 28 OctKerzers 14:27−1 min—
Tue 27 OctKerzers 14:27−2 min—
Mon 26 OctKerzers 14:28No data—
Sun 25 OctKerzers 14:27−1 min—
Sat 24 OctKerzers 14:27−1 min—