КПВ 19202 Асеновград – Крумово

View line КПВ

Асеновград 05:20 → Крумово 05:33 Daily 0 h 13 min · 3 stops BDŽ

✓ Today’s run finished

Today it reached Крумово at 05:33 0 min

  1. Асеновград05:20
  2. Маврудово05:27
  3. Крумово05:33

Next service: tomorrow 05:20 from Асеновград · Wed 11 Nov

Next departure 05:20 tomorrow · Асеновград
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 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 +6 min · last fix heading to Крумово +5 min

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 97% · 33
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (3 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:20on time on time
05:27 / 05:28≈ on time ≈ on time
05:33on 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
Tue 10 NovКрумово 05:340 min—
Mon 9 NovКрумово 05:340 min—
Sun 8 NovКрумово 05:340 min—
Sat 7 NovКрумово 05:340 min—
Fri 6 NovКрумово 05:340 min—
Thu 5 NovКрумово 05:340 min—
Wed 4 NovКрумово 05:340 min—
Tue 3 NovКрумово 05:340 min—
Mon 2 NovКрумово 05:340 min—
Sun 1 NovКрумово 05:340 min—
Sat 31 OctКрумово 05:340 min—
Fri 30 OctКрумово 05:340 min—
Thu 29 OctКрумово 05:340 min—
Wed 28 OctКрумово 05:340 min—
Tue 27 OctКрумово 05:340 min—
Mon 26 OctКрумово 05:340 min—
Sun 25 OctКрумово 05:34No data—
Sat 24 OctКрумово 05:340 min—
Fri 23 OctКрумово 05:340 min—
Thu 22 OctКрумово 05:340 min—
Wed 21 OctКрумово 05:340 min—
Tue 20 OctКрумово 05:340 min—
Mon 19 OctКрумово 05:340 min—
Sun 18 OctКрумово 05:340 min—
Sat 17 OctКрумово 05:340 min—
Fri 16 OctКрумово 05:340 min—
Thu 15 OctКрумово 05:340 min—
Wed 14 OctКрумово 05:340 min—
Tue 13 OctКрумово 05:39+5 min+6 min
Mon 12 OctКрумово 05:340 min—