IC3 557 Zürich HB – Chur

View line IC3

Zürich HB 06:38 → Chur 07:52 Daily 1 h 14 min · 4 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Chur at 07:52 −1 min

  1. Zürich HB06:38
  2. Sargans07:32
  3. Landquart07:41
  4. Chur07:52

Next service: tomorrow 06:38 from Zürich HB · Fri 6 Nov

Next departure 06:38 tomorrow · Zürich HB
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
37/38 runs under 3 min
RT coverage: 38 full · 0 partial · 3 no data
Typical delay
−1min
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 Chur, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 14 Oct Max en route +5 min · last fix heading to Chur +5 min

Distribution · 90 days

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

  • Early 39% · 15
  • On time 58% · 22
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 80% W n=5
  • 100% T n=6
  • 100% F n=4
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 38 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
06:38on time on time
07:32 / 07:33≈ 1 min early ≈ +1 min
07:41 / 07:42≈ 1 min early ≈ +1 min
07:521 min early +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 5 NovChur 07:52−1 min—
Wed 4 NovChur 07:52−1 min—
Tue 3 NovChur 07:52−1 min—
Mon 2 NovChur 07:530 min—
Sun 1 NovChur 07:530 min—
Sat 31 OctChur 07:52−1 min—
Fri 30 OctChur 07:530 min—
Thu 29 OctChur 07:52−1 min—
Wed 28 OctChur 07:52−2 min—
Tue 27 OctChur 07:53−1 min—
Mon 26 OctChur 07:56+3 min+3 min
Sun 25 OctChur 07:52−1 min—
Sat 24 OctChur 07:530 min—
Fri 23 OctChur 07:52−1 min—
Thu 22 OctChur 07:53−1 min—
Wed 21 OctChur 07:53+1 min+1 min
Tue 20 OctChur 07:540 min—
Mon 19 OctChur 07:52−1 min—
Sun 18 OctChur 07:52−1 min—
Sat 17 OctChur 07:52−1 min—
Fri 16 OctChur 07:530 min—
Thu 15 OctChur 07:56+3 min+3 min
Wed 14 OctChur 07:58+5 min+5 min
Tue 13 OctChur 07:55+1 min+1 min
Mon 12 OctChur 07:54+1 min+2 min
Sun 11 OctVisp 17:49−2 min—
Sat 10 OctVisp 17:49−2 min+8 min
Fri 9 OctVisp 17:53+2 min+2 min
Thu 8 OctVisp 17:49−2 min+3 min
Wed 7 OctVisp 17:50−1 min+1 min