КПВ 19221 Пловдив → Крумово

View line КПВ

Пловдив 16:48 → Крумово 17:01 Daily 0 h 13 min · 3 stops BDŽ

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 16:48 from Пловдив · Sat 21 Nov

Next departure 16:48 today · Пловдив
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 1 no data
On-time · 90 days
98%
43/44 runs under 3 min
RT coverage: 44 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 31 Oct Max en route +6 min · last fix heading to Асеновград +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 43
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=5
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 83% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 44 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
16:48on time on time
16:50 / 16:51≈ on time ≈ on time
17:01on 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 20 NovКрумово 17:020 min—
Thu 19 NovАсеновград 17:040 min—
Wed 18 NovАсеновград 17:140 min—
Mon 16 NovАсеновград 17:140 min—
Sun 15 NovАсеновград 17:150 min—
Sat 14 NovАсеновград 17:140 min—
Fri 13 NovАсеновград 17:140 min—
Thu 12 NovАсеновград 17:140 min—
Wed 11 NovАсеновград 17:140 min—
Tue 10 NovАсеновград 17:140 min—
Mon 9 NovАсеновград 17:040 min—
Sun 8 NovАсеновград 17:040 min—
Sat 7 NovАсеновград 17:040 min—
Fri 6 NovАсеновград 17:040 min—
Thu 5 NovАсеновград 17:040 min—
Wed 4 NovАсеновград 17:040 min—
Tue 3 NovАсеновград 17:040 min—
Mon 2 NovАсеновград 17:040 min—
Sun 1 NovАсеновград 17:040 min—
Sat 31 OctАсеновград 17:08+4 min+6 min
Fri 30 OctАсеновград 17:040 min—
Thu 29 OctАсеновград 17:040 min—
Wed 28 OctАсеновград 17:040 min—
Tue 27 OctАсеновград 17:050 min—
Mon 26 OctАсеновград 17:040 min—
Sun 25 OctАсеновград 17:04No data—
Sat 24 OctАсеновград 17:040 min—
Fri 23 OctАсеновград 17:040 min—
Thu 22 OctАсеновград 17:040 min—
Wed 21 OctАсеновград 17:040 min—