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

View line КПВ

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

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 04:50 from Пловдив · Fri 6 Nov

Next departure 04:50 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
97%
28/29 runs under 3 min
RT coverage: 29 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

  • Tue 13 Oct Max en route +14 min · last fix heading to Асеновград +5 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 100% 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, 29 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
04:50on time on time
04:52 / 04:53≈ on time ≈ on time
05:03 / 05:04≈ on time ≈ on time
05:08 / 05:09≈ on time ≈ on time
05:16on 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
Thu 5 NovАсеновград 05:170 min—
Wed 4 NovАсеновград 05:170 min—
Tue 3 NovАсеновград 05:170 min—
Mon 2 NovАсеновград 05:170 min—
Sun 1 NovАсеновград 05:170 min—
Sat 31 OctАсеновград 05:170 min—
Fri 30 OctАсеновград 05:170 min—
Thu 29 OctАсеновград 05:170 min—
Wed 28 OctАсеновград 05:170 min—
Tue 27 OctАсеновград 05:170 min—
Mon 26 OctАсеновград 05:170 min—
Sun 25 OctАсеновград 05:17No data—
Sat 24 OctАсеновград 05:170 min—
Fri 23 OctАсеновград 05:170 min—
Thu 22 OctАсеновград 05:170 min—
Wed 21 OctАсеновград 05:170 min—
Tue 20 OctАсеновград 05:170 min—
Mon 19 OctАсеновград 05:170 min—
Sun 18 OctАсеновград 05:170 min—
Sat 17 OctАсеновград 05:170 min—
Fri 16 OctАсеновград 05:170 min—
Thu 15 OctАсеновград 05:170 min—
Wed 14 OctАсеновград 05:170 min—
Tue 13 OctАсеновград 05:22+5 min+14 min
Mon 12 OctАсеновград 05:170 min—
Sun 11 OctАсеновград 05:170 min—
Sat 10 OctАсеновград 05:170 min—
Fri 9 OctАсеновград 05:170 min—
Thu 8 OctАсеновград 05:170 min—
Wed 7 OctАсеновград 05:170 min—