RB47 1241 Heimerdingen – Korntal

View line RB47

Heimerdingen 09:31 → Korntal 09:54 Daily 0 h 23 min · 7 stops SBB CFF FFS

It has not run yet today

Last recorded run: Wednesday 18 November −1 min

Next service: tomorrow 09:31 from Heimerdingen · Fri 20 Nov

Next departure 09:31 tomorrow · Heimerdingen
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 8 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 12 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 Korntal, 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 27 Oct Max en route +13 min · last fix heading to Scuol-Tarasp +13 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 94% · 32
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 83% T n=6
  • 100% W n=7
  • 100% T n=1
  • 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 (7 stops).

Last 90 days, 34 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
09:31on time on time
09:36≈ on time ≈ on time
09:41≈ on time ≈ on time
09:44 / 09:46≈ on time ≈ +1 min
09:48≈ on time ≈ +1 min
09:51≈ on time ≈ +1 min
09:54on 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
Wed 18 NovKorntal 20:24−1 min+1 min
Tue 17 NovKorntal 20:250 min—
Mon 16 NovKorntal 20:24No data—
Sun 15 NovScuol-Tarasp 14:14−1 min—
Sat 14 NovKorntal 20:24−1 min—
Fri 13 NovKorntal 20:240 min+1 min
Thu 12 NovKorntal 20:24No data—
Wed 11 NovKorntal 20:24−1 min—
Tue 10 NovKorntal 20:240 min—
Mon 9 NovKorntal 20:24No data—
Sun 8 NovScuol-Tarasp 14:14−1 min—
Sat 7 NovKorntal 20:240 min—
Fri 6 NovKorntal 20:240 min+2 min
Thu 5 NovKorntal 20:24No data—
Wed 4 NovKorntal 20:240 min—
Tue 3 NovKorntal 20:24+1 min+1 min
Mon 2 NovKorntal 20:24No data—
Sun 1 NovScuol-Tarasp 14:16+1 min—
Sat 31 OctScuol-Tarasp 14:17+1 min+1 min
Fri 30 OctScuol-Tarasp 14:160 min+1 min
Thu 29 OctScuol-Tarasp 14:16No data—
Wed 28 OctScuol-Tarasp 14:160 min—
Tue 27 OctScuol-Tarasp 14:29+13 min+13 min
Mon 26 OctScuol-Tarasp 14:16No data—
Sun 25 OctScuol-Tarasp 14:16+1 min+2 min
Sat 24 OctScuol-Tarasp 14:160 min—
Fri 23 OctScuol-Tarasp 14:16+1 min—
Thu 22 OctScuol-Tarasp 14:16No data—
Wed 21 OctScuol-Tarasp 14:17+1 min—
Tue 20 OctScuol-Tarasp 14:16−1 min—