N7 2603 Zürich HB – Ebikon

View line N7

Zürich HB 01:35 → Ebikon 02:14 Mon, Sat, Sun 0 h 39 min · 7 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Ebikon at 02:14 0 min

  1. Zürich HB01:35
  2. Baar01:53
  3. Zug01:56
  4. Cham02:01
  5. Rotkreuz02:06
  6. Gisikon-Root02:09
  7. Ebikon02:14

Next service: tomorrow 01:35 from Zürich HB · Sun 8 Nov

Next departure 01:35 tomorrow · Zürich HB
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 1 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 12 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Ebikon, 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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • 100% W n=1
  • — T n=0
  • 100% F n=2
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 12 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
01:35on time on time
01:53≈ on time ≈ +1 min
01:56 / 01:57≈ on time ≈ +1 min
02:01≈ on time ≈ +1 min
02:06≈ on time ≈ +1 min
02:09≈ on time ≈ +1 min
02:14on 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
Sat 7 NovEbikon 02:140 min—
Sun 1 NovLuzern 02:25+1 min—
Sat 31 OctLuzern 02:23−1 min—
Sun 25 OctLuzern 02:24No data—
Sat 24 OctLuzern 02:25+1 min+1 min
Sun 18 OctLuzern 02:250 min—
Sat 17 OctLuzern 02:26+1 min+1 min
Sun 11 OctLuzern 02:26+2 min+2 min
Sat 10 OctLuzern 02:250 min—
Sun 4 OctLuzern 02:23−1 min—
Fri 2 OctCham 01:590 min—
Fri 18 SeptCham 01:590 min+5 min
Wed 16 SeptCham 01:590 min+30 min