КПВ 30232 Зимница → Сливен

View line КПВ

Зимница 12:20 → Сливен 12:39 Daily 0 h 19 min · 4 stops BDŽ

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 12:20 from Зимница · Sat 21 Nov

Next departure 12:20 today · Зимница
On-time · 30 days
85%
23/27 runs under 3 min
RT coverage: 27 full · 0 partial · 1 no data
On-time · 90 days
79%
34/43 runs under 3 min
RT coverage: 43 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +3 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 3 Nov Max en route +9 min · last fix heading to Сливен +8 min
  • Tue 13 Oct Max en route +7 min · last fix heading to Сливен +7 min
  • Mon 12 Oct Max en route +7 min · last fix heading to Сливен +6 min
  • Fri 30 Oct Max en route +4 min · last fix heading to Сливен +4 min
  • Wed 28 Oct Max en route +4 min · last fix heading to Сливен +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 34
  • 3–10 min 21% · 9
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 40% T n=5
  • 71% W n=7
  • 100% T n=7
  • 86% F n=7
  • 83% S n=6
  • 80% S n=5

Stops and timetable

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

Last 90 days, 43 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
12:20on time on time
12:27 / 12:28≈ on time ≈ +2 min
12:34 / 12:35≈ on time ≈ +3 min
12:39on time +4 min

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Сливен 12:390 min—
Thu 19 NovСливен 12:390 min—
Wed 18 NovСливен 12:400 min—
Mon 16 NovСливен 12:390 min—
Sun 15 NovСливен 12:390 min—
Sat 14 NovСливен 12:390 min—
Fri 13 NovСливен 12:390 min—
Thu 12 NovСливен 12:390 min—
Wed 11 NovСливен 12:42+2 min+3 min
Tue 10 NovСливен 12:390 min—
Mon 9 NovСливен 12:390 min—
Sun 8 NovСливен 12:390 min—
Sat 7 NovСливен 12:390 min—
Fri 6 NovСливен 12:390 min—
Thu 5 NovСливен 12:390 min—
Wed 4 NovСливен 12:400 min—
Tue 3 NovСливен 12:48+8 min+9 min
Mon 2 NovСливен 12:390 min—
Sun 1 NovСливен 12:400 min—
Sat 31 OctСливен 12:400 min—
Fri 30 OctСливен 12:44+4 min+4 min
Thu 29 OctСливен 12:400 min—
Wed 28 OctСливен 12:44+4 min+4 min
Tue 27 OctСливен 12:43+3 min+4 min
Mon 26 OctСливен 12:400 min—
Sun 25 OctСливен 12:40No data—
Sat 24 OctСливен 12:400 min—
Fri 23 OctСливен 12:400 min—
Thu 22 OctСливен 12:400 min—
Wed 21 OctСливен 12:400 min—