Os 14759 14759 Boskovice – Skalice n. Svit.

View line Os 14759

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

✓ Today’s run finished

Today, last fix heading to Skalice n. Svit. at 15:09 No data

  1. Boskovice15:01
  2. Skalice n. Svit.15:08

Next service: tomorrow 15:01 from Boskovice · Fri 6 Nov

Next departure 15:01 tomorrow · Boskovice
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
100%
59/59 runs under 3 min
RT coverage: 59 full · 0 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Skalice n. Svit., 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

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

  • Early 0% · 0
  • On time 100% · 59
  • 3–10 min 0% · 0
  • 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
  • 100% T n=8
  • 100% F n=8
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 59 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
15:01on time on time
15:08on time on time

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 5 NovSkalice n. Svit. 15:09No data—
Wed 4 NovSkalice n. Svit. 15:09No data—
Tue 3 NovSkalice n. Svit. 15:09No data—
Mon 2 NovSkalice n. Svit. 15:09No data—
Sun 1 NovSkalice n. Svit. 15:09No data—
Sat 31 OctSkalice n. Svit. 15:09No data—
Fri 30 OctSkalice n. Svit. 15:09No data—
Thu 29 OctSkalice n. Svit. 15:09No data—
Wed 28 OctSkalice n. Svit. 15:09No data—
Tue 27 OctSkalice n. Svit. 15:09No data—
Mon 26 OctSkalice n. Svit. 15:09No data—
Sun 25 OctSkalice n. Svit. 15:09No data—
Sat 24 OctSkalice n. Svit. 15:09No data—
Fri 23 OctSkalice n. Svit. 15:09No data—
Thu 22 OctSkalice n. Svit. 15:09No data—
Wed 21 OctSkalice n. Svit. 15:09No data—
Tue 20 OctSkalice n. Svit. 15:09No data—
Mon 19 OctSkalice n. Svit. 15:09No data—
Sun 18 OctSkalice n. Svit. 15:09No data—
Sat 17 OctSkalice n. Svit. 15:09No data—
Fri 16 OctSkalice n. Svit. 15:09No data—
Thu 15 OctSkalice n. Svit. 15:09No data—
Wed 14 OctSkalice n. Svit. 15:09No data—
Tue 13 OctSkalice n. Svit. 15:09No data—
Mon 12 OctSkalice n. Svit. 15:09No data—
Sun 11 OctSkalice n. Svit. 15:09No data—
Sat 10 OctSkalice n. Svit. 15:09No data—
Fri 9 OctSkalice n. Svit. 15:09No data—
Thu 8 OctSkalice n. Svit. 15:09No data—
Wed 7 OctSkalice n. Svit. 15:09No data—