КПВ 70226 Мездра – Враца

View line КПВ

Мездра 20:10 → Враца 20:30 Daily 0 h 20 min · 4 stops BDŽ

✓ Today’s run finished

Today it reached Враца at 20:30 0 min

  1. Мездра20:10
  2. Моравица20:15
  3. Руска Бяла20:20
  4. Враца20:30

Next service: tomorrow 20:10 from Мездра · Sat 7 Nov

Next departure 20:10 tomorrow · Мездра
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Wed 28 Oct Max en route +7 min · last fix heading to Враца +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 75% W n=4
  • 100% T n=5
  • 100% F n=5
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 30 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
20:10on time on time
20:15 / 20:16≈ on time ≈ on time
20:20 / 20:21≈ on time ≈ on time
20:30on 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 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
Fri 6 NovВраца 20:290 min—
Thu 5 NovВраца 20:290 min—
Wed 4 NovВраца 20:29No data—
Tue 3 NovВраца 20:290 min—
Mon 2 NovВраца 20:300 min—
Sun 1 NovВраца 20:290 min—
Sat 31 OctВраца 20:310 min—
Fri 30 OctВраца 20:310 min—
Thu 29 OctВраца 20:310 min—
Wed 28 OctВраца 20:37+6 min+7 min
Tue 27 OctВраца 20:310 min—
Mon 26 OctВраца 20:310 min—
Sun 25 OctВраца 20:31No data—
Sat 24 OctВраца 20:310 min—
Fri 23 OctВраца 20:310 min—
Thu 22 OctВраца 20:310 min—
Wed 21 OctВраца 20:310 min—
Tue 20 OctВраца 20:310 min—
Mon 19 OctВраца 20:320 min—
Sun 18 OctВраца 20:320 min—
Sat 17 OctВраца 20:310 min—
Fri 16 OctВраца 20:310 min—
Thu 15 OctВраца 20:310 min—
Wed 14 OctВраца 20:310 min—
Tue 13 OctВраца 20:310 min—
Mon 12 OctВраца 20:310 min—
Sun 11 OctВраца 20:310 min—
Sat 10 OctВраца 20:310 min—
Fri 9 OctВраца 20:310 min—
Thu 8 OctВраца 20:310 min—