КПВ 20230 Червен Бряг – Мездра

View line КПВ

Червен Бряг 05:50 → Мездра 06:50 Daily 1 h 00 min · 11 stops BDŽ

✓ Today’s run finished

Today it reached Мездра at 06:50 0 min

  1. Червен Бряг05:50
  2. Карлуково06:04
  3. Кунино06:13
  4. Роман06:24
  5. Синьо Бърдо06:37
  6. Ослен06:41
  7. Мездра06:50

Next service: tomorrow 05:50 from Червен Бряг · Tue 10 Nov

Full trip card
Next departure 05:50 tomorrow · Червен Бряг
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 1 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 34 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
Червен Бряг
05:50on time on time
Реселец
05:56 / 05:57≈ on time ≈ on time
Карлуково
06:04 / 06:05≈ on time ≈ on time
Кунино
06:13 / 06:14≈ on time ≈ on time
Радовене
06:19 / 06:20≈ on time ≈ on time
Роман
06:24 / 06:25≈ on time ≈ on time
Струпец
06:32 / 06:33≈ on time ≈ on time
Синьо Бърдо
06:37 / 06:38≈ on time ≈ on time
Ослен
06:41 / 06:42≈ on time ≈ on time
Брусен
06:46 / 06:47≈ on time ≈ on time
Мездра
06:50on 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
Mon 9 NovМездра 06:490 min—
Sun 8 NovМездра 06:490 min—
Sat 7 NovМездра 06:490 min—
Fri 6 NovМездра 06:490 min—
Thu 5 NovМездра 06:490 min—
Wed 4 NovМездра 06:490 min—
Tue 3 NovМездра 06:490 min—
Mon 2 NovМездра 06:490 min—
Sun 1 NovМездра 06:510 min—
Sat 31 OctМездра 06:510 min—
Fri 30 OctМездра 06:510 min—
Thu 29 OctМездра 06:510 min—
Wed 28 OctМездра 06:510 min—
Tue 27 OctМездра 06:510 min—
Mon 26 OctМездра 06:510 min—
Sun 25 OctМездра 06:520 min—
Sat 24 OctМездра 06:510 min—
Fri 23 OctМездра 06:510 min—
Thu 22 OctМездра 06:510 min—
Wed 21 OctМездра 06:510 min—
Tue 20 OctМездра 06:510 min—
Mon 19 OctМездра 06:510 min—
Sun 18 OctМездра 06:510 min—
Sat 17 OctМездра 06:520 min—
Fri 16 OctМездра 06:510 min—
Thu 15 OctМездра 06:510 min—
Wed 14 OctМездра 06:510 min—
Tue 13 OctМездра 06:510 min—
Mon 12 OctМездра 06:510 min—
Sun 11 OctМездра 06:510 min—