Os 14734 14734 Skalice n. Svit. – Boskovice

View line Os 14734

Skalice n. Svit. 06:50 → Boskovice 06:57 Daily 0 h 07 min · 2 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 06:50 from Skalice n. Svit. · Sat 7 Nov

Next departure 06:50 today · Skalice n. Svit.
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
96%
55/57 runs under 3 min
RT coverage: 57 full · 0 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Boskovice, 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 18 Sept Max en route +3 min · last fix heading to — +3 min
  • Thu 17 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 95% · 54
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=8
  • 100% W n=8
  • 88% T n=8
  • 88% F n=8
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 57 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
06:50on time +2 min
06:57on 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 6 NovBoskovice 06:58No data—
Thu 5 NovBoskovice 06:58No data—
Wed 4 NovBoskovice 06:58No data—
Tue 3 NovBoskovice 06:58No data—
Mon 2 NovBoskovice 06:58No data—
Sun 1 NovBoskovice 06:58No data—
Sat 31 OctBoskovice 06:58No data—
Fri 30 OctBoskovice 06:58No data—
Thu 29 OctBoskovice 06:58No data—
Wed 28 OctBoskovice 06:58No data—
Tue 27 OctBoskovice 06:58No data—
Mon 26 OctBoskovice 06:58No data—
Sun 25 OctBoskovice 06:58No data—
Sat 24 OctBoskovice 06:58No data—
Fri 23 OctBoskovice 06:58No data—
Thu 22 OctBoskovice 06:58No data—
Wed 21 OctBoskovice 06:58No data—
Tue 20 OctBoskovice 06:58No data—
Mon 19 OctBoskovice 06:58No data—
Sun 18 OctBoskovice 06:58No data—
Sat 17 OctBoskovice 06:58No data—
Fri 16 OctBoskovice 06:58No data—
Thu 15 OctBoskovice 06:58No data—
Wed 14 OctBoskovice 06:58No data—
Tue 13 OctBoskovice 06:58No data—
Mon 12 OctBoskovice 06:58No data—
Sun 11 OctBoskovice 06:58No data—
Sat 10 OctBoskovice 06:58No data—
Fri 9 OctBoskovice 06:58No data—
Thu 8 OctBoskovice 06:58No data—