КПВ 10231 Септември – Пловдив

View line КПВ

Септември 05:40 → Пловдив 06:30 Daily 0 h 50 min · 13 stops BDŽ

✓ Today’s run finished

Today it reached Пловдив at 06:30 0 min

  1. Септември05:40
  2. Звъничево05:47
  3. Пазарджик05:55
  4. Огняново06:04
  5. Стамболийски06:13
  6. Тодор Каблешков06:21
  7. Пловдив06:30

Next service: tomorrow 05:40 from Септември · Fri 6 Nov

Next departure 05:40 tomorrow · Септември
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 1 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

  • Sun 18 Oct Max en route +4 min · last fix heading to Пловдив +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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:40on time on time
05:43 / 05:44≈ on time ≈ on time
05:47 / 05:48≈ on time ≈ on time
05:51 / 05:52≈ on time ≈ on time
05:55 / 05:56≈ on time ≈ on time
06:00 / 06:01≈ on time ≈ on time
06:04 / 06:05≈ on time ≈ on time
06:07 / 06:08≈ on time ≈ on time
06:13 / 06:14≈ on time ≈ on time
06:17 / 06:18≈ on time ≈ on time
06:21 / 06:22≈ on time ≈ on time
06:25 / 06:26≈ on time ≈ on time
06:30on 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Пловдив 06:290 min—
Wed 4 NovПловдив 06:290 min—
Tue 3 NovПловдив 06:290 min—
Mon 2 NovПловдив 06:290 min—
Sun 1 NovПловдив 06:310 min—
Sat 31 OctПловдив 06:310 min—
Fri 30 OctПловдив 06:310 min—
Thu 29 OctПловдив 06:310 min—
Wed 28 OctПловдив 06:310 min—
Tue 27 OctПловдив 06:310 min—
Mon 26 OctПловдив 06:310 min—
Sun 25 OctПловдив 06:310 min—
Sat 24 OctПловдив 06:310 min—
Fri 23 OctПловдив 06:310 min—
Thu 22 OctПловдив 06:33+2 min+2 min
Wed 21 OctПловдив 06:310 min—
Tue 20 OctПловдив 06:310 min—
Mon 19 OctПловдив 06:310 min—
Sun 18 OctПловдив 06:34+3 min+4 min
Sat 17 OctПловдив 06:310 min—
Fri 16 OctПловдив 06:310 min—
Thu 15 OctПловдив 06:33+2 min+4 min
Wed 14 OctПловдив 06:310 min—
Tue 13 OctПловдив 06:310 min—
Mon 12 OctПловдив 06:310 min—
Sun 11 OctПловдив 06:310 min—
Sat 10 OctПловдив 06:310 min—
Fri 9 OctПловдив 06:310 min—
Thu 8 OctПловдив 06:310 min—
Wed 7 OctПловдив 06:310 min—