Столько людей остались не только без домов и машин, но и без своего скота который был их единственным доходом на пропитание 💔

Channel
КАВКАЗ ЧП
@kavkazchp
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
187subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001972661651 |
|---|---|
| Type | Channel |
| Username | @kavkazchp |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/kavkazchp |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 10:16 | 187 | -1 |
| 15 Aug 2026, 20:36 | 188 | -2 |
| 8 Aug 2026, 12:01 | 190 | no change |
| 7 Aug 2026, 14:11 | 190 | -1 |
| 7 Aug 2026, 10:10 | 191 | first reading |
Engagement
18 posts held, back to 3 February 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 7 April 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 6m 56s
- Average length
- 30s
Measured directly from 14 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
5 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 40.0% | |
| 👍 | 2 | 40.0% | |
| 👎 | 1 | 20.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 3 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 3 February 2026 to 7 April 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Двое сыновей рискуя своей жизнью спасли своего отца во время потопа в Махачкале на Учхозе.
Состояние домов в с. Араблинское сейчас, весь ил в домах, нужна помощь чтоб расчистить всё это
⚡️Тело пропавшей бабушки из Мамедкалы Аминат Мусаевой обнаружили под заносами за 4 километров от Мамедкалы Количество жертв наводнения в Дагестане достигло шести.
Мусаева Аминат проживающая в Мамедкале по улице Красноармейская 16. Пропала без вести, сообщается что возможно унесло течением, если кто-то знает где она, может видел кто ее, если спасли позвоните пожалуйста. Связь: 89633738898 ‼️Максимальный репост
Кадры спасения мужчины и женщины, которых унесло течением в Мамедкале
Люди приехали с разных уголков Дагестана, заходят в каждый дом и вычищают у кого-то обломки стен, у кого-то мебель!
Масштабы привезенной гуманитарной помощи в Мамедкале Весь народ сплотился, за пределами Дагестана тоже
Из Чечни выехала большая колонна помощи для Дагестана
⚡️ «Все разрушилось, ничего не осталось» Жительница с ребенком поселка Мамедкала о ситуации после подтопления.
⚡️Ощущение, что в Мамедкалу приехал весь Дагестан, и не только. Такой сплоченности и единства здесь можно только позавидовать. Многокилометровые пробки тех, кто едет помочь, кто едой, кто одеждой, медикаментами, одеялами и другими вещами первой необходимости. - ННТ
Жесткая авария в Даг. Огни с участием внедорожника, один лежит на земле
Showing the 12 most recent of 18 posts we hold for @kavkazchp. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 24 August 2026 — this entry's latest reading, not the date you are reading this.
“КАВКАЗ ЧП” (@kavkazchp), 187 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/kavkazchp.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.