S5 15793 Neuchâtel – Kerzers

View line S5

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

✓ Today’s run finished

Today, last fix heading to Kerzers at 00:29 No data

  1. Neuchâtel21:04
  2. St-Blaise-Lac21:07
  3. Marin-Epagnier21:10
  4. Gampelen21:14
  5. Ins21:18
  6. Müntschemier21:20
  7. Kerzers21:27

Next service: tomorrow 21:04 from Neuchâtel · Fri 20 Nov

Next departure 21:04 tomorrow · Neuchâtel
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
95%
53/56 runs under 3 min
RT coverage: 56 full · 0 partial · 5 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

  • Thu 3 Sept Max en route +11 min · last fix heading to Kerzers +8 min
  • Sat 24 Oct Max en route +9 min · last fix heading to Kerzers +8 min
  • Mon 12 Oct Max en route +3 min · last fix heading to Kerzers +3 min

Distribution · 90 days

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

  • Early 25% · 14
  • On time 70% · 39
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 100% T n=9
  • 100% W n=9
  • 86% T n=7
  • 100% F n=5
  • 88% S n=8
  • 100% S n=9

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