S25 20559 Zürich HB → Linthal

View line S25

Zürich HB 15:43 → Linthal 17:16 Daily 1 h 33 min · 19 stops SBB CFF FFS

S25 20559 Zürich HB–Linthal: final delay under 3 min on 28 of its 28 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 15:18 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 15:43 from Zürich HB · Sun 22 Nov

Next departure 15:43 today · Zürich HB
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
100%
48/48 runs under 3 min
RT coverage: 48 full · 0 partial · 1 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 Linthal, 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 2% · 1
  • On time 98% · 47
  • 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=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=6
  • 100% S n=7

Stops and timetable

Timetable of the latest run from the operator’s GTFS (19 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
15:43on time on time
16:00≈ on time ≈ on time
16:07≈ on time ≈ on time
16:12≈ on time ≈ on time
16:16≈ on time ≈ on time
16:25 / 16:34≈ on time ≈ on time
16:38≈ on time ≈ on time
16:41≈ on time ≈ on time
16:45 / 16:46≈ on time ≈ +1 min
16:47≈ on time ≈ +1 min
16:51≈ on time ≈ +1 min
16:54 / 16:59≈ on time ≈ +1 min
17:01≈ on time ≈ +1 min
17:04≈ on time ≈ +1 min
17:06≈ on time ≈ +1 min
17:09≈ on time ≈ +1 min
17:11≈ on time ≈ +1 min
17:13≈ on time ≈ +1 min
17:16on 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 21 NovLinthal 17:170 min—
Fri 20 NovLinthal 17:19+2 min+2 min
Thu 19 NovLinthal 17:170 min—
Wed 18 NovLinthal 17:17+1 min—
Tue 17 NovLinthal 17:170 min—
Mon 16 NovLinthal 17:17+1 min—
Sun 15 NovLinthal 17:170 min—
Sat 14 NovLinthal 17:17No data—
Fri 13 NovLinthal 17:18+1 min—
Thu 12 NovLinthal 17:18+1 min—
Wed 11 NovLinthal 17:170 min—
Tue 10 NovLinthal 17:140 min—
Mon 9 NovLinthal 17:170 min—
Sun 8 NovLinthal 17:140 min—
Sat 7 NovLinthal 17:170 min—
Fri 6 NovLinthal 17:170 min—
Thu 5 NovLinthal 17:170 min—
Wed 4 NovLinthal 17:170 min—
Tue 3 NovLinthal 17:170 min—
Mon 2 NovLinthal 17:170 min—
Sun 1 NovLinthal 17:17+1 min—
Sat 31 OctLinthal 17:170 min—
Fri 30 OctLinthal 17:170 min—
Thu 29 OctLinthal 17:16−1 min—
Wed 28 OctLinthal 17:18+1 min—
Tue 27 OctLinthal 17:170 min—
Mon 26 OctLinthal 17:16−1 min—
Sun 25 OctLinthal 17:17+1 min—
Sat 24 OctLinthal 17:18+1 min+1 min
Fri 23 OctLinthal 17:160 min—