IR13 2203 St. Gallen – Chur

View line IR13

St. Gallen 19:55 → Chur 21:18 Daily 1 h 23 min · 11 stops SOB

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 19:55 from St. Gallen · Fri 20 Nov

Next departure 19:55 today · St. Gallen
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%
46/46 runs under 3 min
RT coverage: 46 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: 0 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

Distribution · 90 days

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

  • Early 17% · 8
  • On time 83% · 38
  • 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=6
  • 100% W n=7
  • 100% T n=7
  • 100% F n=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 46 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
19:55on time +1 min
20:08 / 20:09≈ on time ≈ +1 min
20:16≈ on time ≈ +1 min
20:22 / 20:23≈ on time ≈ +1 min
20:28 / 20:29≈ on time ≈ +1 min
20:44 / 20:45≈ on time ≈ +1 min
20:54 / 20:56≈ on time ≈ +1 min
21:00≈ on time ≈ +1 min
21:03≈ on time ≈ +1 min
21:08≈ on time ≈ +1 min
21:18on 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
Thu 19 NovChur 08:190 min+1 min
Wed 18 NovChur 08:190 min—
Tue 17 NovChur 08:19No data—
Mon 16 NovChur 08:19+1 min—
Sun 15 NovChur 08:18−1 min—
Sat 14 NovChur 08:190 min—
Fri 13 NovChur 08:190 min—
Thu 12 NovChur 08:190 min—
Wed 11 NovChur 08:190 min—
Tue 10 NovChur 08:190 min—
Mon 9 NovChur 08:17−2 min—
Sun 8 NovChur 08:190 min—
Sat 7 NovChur 08:18−1 min—
Fri 6 NovChur 08:190 min—
Thu 5 NovChur 08:18−1 min—
Wed 4 NovChur 08:18−2 min—
Tue 3 NovChur 08:18−1 min—
Mon 2 NovChur 08:190 min—
Sun 1 NovChur 08:18−1 min—
Sat 31 OctChur 08:190 min—
Fri 30 OctChur 08:18−1 min—
Thu 29 OctChur 08:20+1 min—
Wed 28 OctChur 08:190 min—
Tue 27 OctChur 08:190 min—
Mon 26 OctChur 08:190 min+2 min
Sun 25 OctChur 08:180 min—
Sat 24 OctChur 08:18−1 min—
Fri 23 OctChur 08:18−1 min—
Thu 22 OctChur 08:190 min—
Wed 21 OctChur 08:190 min+3 min