IC3 579 Basel SBB – Chur

View line IC3

Basel SBB 16:33 → Chur 18:52 Daily 2 h 19 min · 5 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Chur at 18:57 +5 min

  1. Basel SBB16:33
  2. Zürich HB17:26
  3. Sargans18:32
  4. Landquart18:41
  5. Chur18:52

Next service: tomorrow 16:33 from Basel SBB · Tue 10 Nov

Next departure 16:33 tomorrow · Basel SBB
On-time · 30 days
80%
24/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
89%
56/63 runs under 3 min
RT coverage: 63 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Tue 20 Oct Max en route +29 min · last fix heading to Chur +29 min
  • Thu 22 Oct Max en route +17 min · last fix heading to Chur +17 min
  • Thu 8 Oct Max en route +6 min · last fix heading to Chur +6 min
  • Fri 16 Oct Max en route +5 min · last fix heading to Chur +5 min
  • Mon 9 Nov Max en route +5 min · last fix heading to Chur +5 min

Distribution · 90 days

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

  • Early 17% · 11
  • On time 71% · 45
  • 3–10 min 8% · 5
  • 10–30 min 3% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 90% T n=10
  • 91% W n=11
  • 75% T n=8
  • 89% F n=9
  • 89% S n=9
  • 100% S n=10

Stops and timetable

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

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