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

View line КПВ

Пловдив 07:45 → Асеновград 08:11 Daily 0 h 26 min · 5 stops BDŽ

✓ Today’s run finished

Today it reached Асеновград at 08:14 +3 min

  1. Пловдив07:45
  2. Вагоно-ремонтно депо Пловдив07:47
  3. Крумово07:58
  4. Маврудово08:03
  5. Асеновград08:11

Next service: tomorrow 07:45 from Пловдив · Fri 6 Nov

Next departure 07:45 tomorrow · Пловдив
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
93%
27/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

  • Wed 14 Oct Max en route +4 min · last fix heading to Асеновград +4 min
  • Thu 5 Nov Max en route +4 min · last fix heading to Асеновград +3 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 93% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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