КПВ 24225 Левски – Троян

View line КПВ

Левски 15:15 → Троян 17:05 Daily 1 h 50 min · 20 stops BDŽ

✓ Today’s run finished

Today it reached Троян at 17:05 0 min

  1. Левски15:15
  2. Александрово15:33
  3. Йоглав15:50
  4. Ловеч16:09
  5. Хлевене16:26
  6. Ломец16:47
  7. Троян17:05

Next service: tomorrow 15:15 from Левски · Thu 12 Nov

Next departure 15:15 tomorrow · Левски
On-time · 30 days
83%
25/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
86%
32/37 runs under 3 min
RT coverage: 37 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Троян, 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 20 Oct Max en route +18 min · last fix heading to Троян +14 min
  • Mon 9 Nov Max en route +12 min · last fix heading to Троян +6 min
  • Wed 21 Oct Max en route +17 min · last fix heading to Троян +5 min
  • Fri 6 Nov Max en route +5 min · last fix heading to Троян +4 min
  • Wed 28 Oct Max en route +6 min · last fix heading to Троян +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 32
  • 3–10 min 11% · 4
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 80% T n=5
  • 67% W n=6
  • 100% T n=5
  • 80% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 37 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:15on time +4 min
15:19 / 15:20≈ on time ≈ +4 min
15:23 / 15:24≈ on time ≈ +4 min
15:33 / 15:34≈ on time ≈ +4 min
15:38 / 15:39≈ on time ≈ +4 min
15:46 / 15:47≈ on time ≈ +3 min
15:50 / 15:51≈ on time ≈ +3 min
15:55 / 15:56≈ on time ≈ +3 min
16:02 / 16:03≈ on time ≈ +3 min
16:03 / 16:04≈ on time ≈ +3 min
16:09 / 16:10≈ on time ≈ +3 min
16:14 / 16:15≈ on time ≈ +3 min
16:22 / 16:23≈ on time ≈ +3 min
16:26 / 16:27≈ on time ≈ +3 min
16:33 / 16:34≈ on time ≈ +3 min
16:40 / 16:41≈ on time ≈ +3 min
16:47 / 16:48≈ on time ≈ +3 min
16:51 / 16:52≈ on time ≈ +3 min
16:56 / 16:57≈ on time ≈ +3 min
17:05on time +3 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 5 October 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 11 NovТроян 17:040 min—
Tue 10 NovТроян 17:040 min—
Mon 9 NovТроян 17:12+6 min+12 min
Sun 8 NovТроян 17:040 min—
Sat 7 NovТроян 17:040 min—
Fri 6 NovТроян 17:09+4 min+5 min
Thu 5 NovТроян 17:040 min—
Wed 4 NovТроян 17:040 min—
Tue 3 NovТроян 17:040 min—
Mon 2 NovТроян 17:040 min—
Sun 1 NovТроян 17:060 min+2 min
Sat 31 OctТроян 17:060 min—
Fri 30 OctТроян 17:060 min—
Thu 29 OctТроян 17:060 min—
Wed 28 OctТроян 17:09+3 min+6 min
Tue 27 OctТроян 17:070 min+3 min
Mon 26 OctТроян 17:060 min+4 min
Sun 25 OctТроян 17:060 min—
Sat 24 OctТроян 17:060 min—
Fri 23 OctТроян 17:060 min—
Thu 22 OctТроян 17:060 min—
Wed 21 OctТроян 17:10+5 min+17 min
Tue 20 OctТроян 17:20+14 min+18 min
Mon 19 OctТроян 17:060 min—
Sun 18 OctТроян 17:060 min—
Sat 17 OctТроян 17:060 min—
Fri 16 OctТроян 17:060 min—
Thu 15 OctТроян 17:060 min+4 min
Wed 14 OctТроян 17:060 min—
Tue 13 OctТроян 17:060 min—