Os 15327 15327 Borová u Poličky – Svitavy

View line Os 15327

Borová u Poličky 05:52 → Svitavy 06:34 Sat, Sun 0 h 42 min · 13 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Svitavy at 06:34 No data

  1. Borová u Poličky05:52
  2. Oldřiš05:57
  3. Polička06:07
  4. Pomezí06:14
  5. Květná06:19
  6. Vendolí06:24
  7. Svitavy06:34

Next service: Saturday 05:52 from Borová u Poličky · Sat 14 Nov

Full trip card
Next departure 05:52 Saturday · Borová u Poličky
On-time · 30 days
—
Too little data (0/11 runs with data)
RT coverage: 0 full · 0 partial · 11 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Svitavy, 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

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

  • Early 0% · 0
  • On time 100% · 17
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 17 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
Borová u Poličky
05:52on time on time
Borová u Poličky zastávka
05:54≈ on time ≈ on time
Oldřiš
05:57≈ on time ≈ on time
Sádek u Poličky
06:01≈ on time ≈ on time
Polička
06:07 / 06:08≈ on time ≈ +1 min
Pomezí zastávka
06:10≈ on time ≈ +1 min
Pomezí
06:14≈ on time ≈ +1 min
Květná zastávka
06:17≈ on time ≈ +1 min
Květná
06:19≈ on time ≈ +1 min
Vendolí zastávka
06:22≈ on time ≈ +1 min
Vendolí
06:24≈ on time ≈ +2 min
Svitavy zastávka
06:30≈ on time ≈ +2 min
Svitavy
06:34on time +2 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
Sun 8 NovSvitavy 06:34No data—
Sat 7 NovSvitavy 06:34No data—
Sun 1 NovSvitavy 06:35No data—
Sat 31 OctSvitavy 06:35No data—
Wed 28 OctSvitavy 06:35No data—
Sun 25 OctSvitavy 06:35No data—
Sat 24 OctSvitavy 06:35No data—
Sun 18 OctSvitavy 06:35No data—
Sat 17 OctSvitavy 06:35No data—
Sun 11 OctSvitavy 06:35No data—
Sat 10 OctSvitavy 06:35No data—
Sun 4 Oct— 06:51+2 min+2 min
Sat 3 Oct— 06:49+1 min+2 min
Mon 28 Sept— 06:490 min+1 min
Sun 27 Sept— 06:50+1 min+2 min
Sat 26 Sept— 06:49+1 min+2 min
Sun 20 Sept— 06:490 min+1 min
Sat 19 Sept— 06:51+2 min+2 min
Sun 13 Sept— 06:50+2 min+2 min
Sat 12 Sept— 06:48−1 min—
Sun 6 Sept— 06:480 min—
Sat 5 Sept— 06:490 min—
Sun 30 Aug— 06:47−1 min—
Sat 29 Aug— 06:480 min—
Sun 23 Aug— 06:47−1 min—
Sat 22 Aug— 06:47−1 min—
Sun 16 Aug— 06:490 min+1 min
Sat 15 Aug— 06:480 min+1 min