IC3 577 Zürich HB – Chur

View line IC3

Zürich HB 16:38 → Chur 17:52 Mon, Tue, Wed, Thu, Fri 1 h 14 min · 4 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Chur at 17:52 0 min

  1. Zürich HB16:38
  2. Sargans17:32
  3. Landquart17:41
  4. Chur17:52

Next service: tomorrow 16:38 from Zürich HB · Thu 12 Nov

Next departure 16:38 tomorrow · Zürich HB
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
89%
31/35 runs under 3 min
RT coverage: 35 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Fri 16 Oct Max en route +6 min · last fix heading to Chur +6 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Visp +4 min
  • Tue 27 Oct Max en route +4 min · last fix heading to Chur +3 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Visp +3 min

Distribution · 90 days

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

  • Early 31% · 11
  • On time 57% · 20
  • 3–10 min 11% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 67% T n=6
  • 100% W n=6
  • 100% T n=5
  • 83% F n=6
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

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