RB47 1277 Heimerdingen – Korntal

View line RB47

Heimerdingen 23:01 → Korntal 23:24 Mon, Tue, Wed, Thu, Fri, Sat 0 h 23 min · 7 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Korntal at 23:24 −1 min

  1. Heimerdingen23:01
  2. Hemmingen23:06
  3. Schwieberdingen23:11
  4. Münchingen23:14
  5. Münchingen Rührberg23:18
  6. Korntal-Gymnasium23:21
  7. Korntal23:24

Next service: tomorrow 23:01 from Heimerdingen · Sat 21 Nov

Next departure 23:01 tomorrow · Heimerdingen
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 9 full · 0 partial · 12 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 13 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: +2 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

  • Fri 13 Nov Max en route +5 min · last fix heading to Scuol-Tarasp +5 min

Distribution · 90 days

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

  • Early 21% · 4
  • On time 74% · 14
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • — T n=0
  • 100% W n=1
  • — T n=0
  • 86% F n=7
  • 100% S n=7
  • 100% S n=2

Stops and timetable

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

Last 90 days, 19 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
23:01on time on time
23:06≈ on time ≈ on time
23:11≈ on time ≈ on time
23:14 / 23:16≈ on time ≈ +1 min
23:18≈ on time ≈ +1 min
23:21≈ on time ≈ +1 min
23:24on 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
Fri 20 NovKorntal 23:24−1 min—
Thu 19 NovKorntal 23:24No data—
Wed 18 NovKorntal 23:24No data—
Tue 17 NovKorntal 23:24No data—
Mon 16 NovKorntal 23:24No data—
Sat 14 NovKorntal 23:24−2 min—
Fri 13 NovScuol-Tarasp 23:24+5 min+5 min
Thu 12 NovKorntal 23:25No data—
Wed 11 NovKorntal 23:24No data—
Tue 10 NovKorntal 23:24No data—
Mon 9 NovKorntal 23:25No data—
Sat 7 NovKorntal 23:240 min—
Fri 6 NovKorntal 23:240 min—
Thu 5 NovKorntal 23:24No data—
Wed 4 NovKorntal 23:24No data—
Tue 3 NovKorntal 23:24No data—
Mon 2 NovKorntal 23:24No data—
Sat 31 OctScuol-Tarasp 23:190 min—
Fri 30 OctScuol-Tarasp 23:18−1 min—
Sat 24 OctScuol-Tarasp 23:190 min—
Fri 23 OctScuol-Tarasp 23:20+1 min—
Sat 17 OctScuol-Tarasp 23:18−1 min—
Fri 16 OctScuol-Tarasp 23:20+1 min—
Sat 10 OctScuol-Tarasp 23:20+1 min+1 min
Fri 9 OctScuol-Tarasp 23:200 min—
Sun 4 OctScuol-Tarasp 23:19No data—
Sat 3 OctScuol-Tarasp 23:19−1 min—
Mon 7 SeptScuol-Tarasp 00:170 min+3 min
Sun 6 SeptScuol-Tarasp 00:17−1 min+9 min
Mon 31 AugScuol-Tarasp 00:17+1 min+5 min