КПВ 19204 Асеновград – Пловдив

View line КПВ

Асеновград 06:05 → Пловдив 06:31 Daily 0 h 26 min · 5 stops BDŽ

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 06:05 from Асеновград · Thu 5 Nov

Next departure 06:05 today · Асеновград
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 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

  • Sat 24 Oct Max en route +13 min · last fix heading to Пловдив +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 27
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
06:05on time on time
06:12 / 06:13≈ on time ≈ on time
06:18 / 06:19≈ on time ≈ on time
06:27 / 06:28≈ on time ≈ on time
06:31on 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
Wed 4 NovПловдив 06:320 min—
Tue 3 NovПловдив 06:320 min—
Mon 2 NovПловдив 06:320 min—
Sun 1 NovПловдив 06:320 min—
Sat 31 OctПловдив 06:320 min—
Fri 30 OctПловдив 06:320 min—
Thu 29 OctПловдив 06:320 min—
Wed 28 OctПловдив 06:320 min—
Tue 27 OctПловдив 06:320 min—
Mon 26 OctПловдив 06:320 min—
Sun 25 OctПловдив 06:32No data—
Sat 24 OctПловдив 06:44+12 min+13 min
Fri 23 OctПловдив 06:320 min—
Thu 22 OctПловдив 06:320 min—
Wed 21 OctПловдив 06:320 min—
Tue 20 OctПловдив 06:320 min—
Mon 19 OctПловдив 06:320 min—
Sun 18 OctПловдив 06:320 min—
Sat 17 OctПловдив 06:320 min—
Fri 16 OctПловдив 06:320 min—
Thu 15 OctПловдив 06:320 min—
Wed 14 OctПловдив 06:320 min—
Tue 13 OctПловдив 06:320 min—
Mon 12 OctПловдив 06:320 min—
Sun 11 OctПловдив 06:320 min—
Sat 10 OctПловдив 06:320 min—
Fri 9 OctПловдив 06:320 min—
Thu 8 OctПловдив 06:320 min—
Wed 7 OctПловдив 06:320 min—
Tue 6 OctПловдив 06:33No data—