Telegram RegisterThe public register of Telegram
Telegram profile photo for Krasnodar Alerts

Channel

Krasnodar Alerts

@krd_alerts

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

3subscribers

+0 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-1003982165082
TypeChannel
Username@krd_alerts
CreatedBetween 1 April 2026 and 20 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live15 September 2026
Measurements held2
On Telegramt.me/krd_alerts

Growth

37 August 2026 — 3 subscribers13 August 2026 — 3 subscribers7 August 202613 August 2026
2 measurements spanning 6 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 15:313no change
7 Aug 2026, 19:343first reading

Engagement

20 posts held, back to 20 June 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 page of 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 20 posts for this entry, the most recent from 22 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4
Videos
2
Links
61

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
11s
Average length
11s

Measured directly from 1 video 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.

Recent posts

22 Jun 2026, 18:48 UTC4 viewsread 13 August 2026

‼️Славянск-на-Кубани Меры безопасности! Уйти с улиц! 🌐 Радар Юг | 📲 МЫ в MAX

22 Jun 2026, 18:39 UTC4 viewsread 13 August 2026

‼️Афипский Ильский Внимание по небу! 🌐 Радар Юг | 📲 МЫ в MAX

22 Jun 2026, 18:34 UTC4 viewsread 13 August 2026

‼️Елизаветинская Республика Адыгея Возможно фиксация от 3 БПЛА в сторону Майоп. 🌐 Радар Юг | 📲 МЫ в MAX

22 Jun 2026, 18:27 UTC4 viewsread 13 August 2026

‼️Республика Адыгея Опасность по БПЛА! Меры безопасности! 🌐 Радар Юг | 📲 МЫ в MAX

22 Jun 2026, 18:27 UTC4 viewsread 13 August 2026

🔴Республика Адыгея - опасность по БПЛА. 🌐 Радар Юг | 📲 МЫ в MAX

22 Jun 2026, 18:20 UTC3 viewsread 13 August 2026

🔴Яблоновский Меры безопасности! 🌐 Радар Юг | 📲 МЫ в MAX

22 Jun 2026, 17:48 UTC3 viewsread 13 August 2026

‼️Абинский район Ахтырская Пролет БПЛА на Ильский/Афипский 🌐 Радар Юг | 📲 МЫ в MAX

22 Jun 2026, 17:43 UTC3 viewsread 13 August 2026

‼️Славянск-на-Кубани Возможны фиксации на вас Меры безопасности! от Темрюкского района 🌐 Радар Юг | 📲 МЫ в MAX

22 Jun 2026, 17:32 UTC3 viewsread 13 August 2026

🚨От Темрюка БПЛА могут пойти в следующих направлениях: 🔴Варениковская Крымск Киевское Славянск-на-Кубани Абинск Ильский Афипский Северская 🔴В обход Керчи Анапа Новороссийск Геленджик Туапсе Сочи Адлер Лазаревское 🌐 Радар Юг | 📲 МЫ в MAX

22 Jun 2026, 16:26 UTC3 viewsread 13 August 2026

🚨Краснодарский край Республика Адыгея - опасность по БПЛА сохраняется. 🌐 Радар Юг | 📲 МЫ в MAX

22 Jun 2026, 10:03 UTC3 viewsread 13 August 2026
Video

❗️ВНИМАНИЕ, ТРЕВОГА❗️ Многие регионы РФ подверглись массовым РАКЕТНЫМ атакам от ВСУ, в некоторых областях был введен режим ЧП. Также продолжаются атаки дронами, ситуация напряженная! В связи с этим было принято решение, создать телеграм каналы для оповещения граждан об атаках. Важно, каналы НЕ БУДУТ БЛОКИРОВАТЬ! Ищите свой регион и подписывайтесь, сейчас крайне важно быть начеку: Москва 24/7 Питер 24/7 Абакан 24…

22 Jun 2026, 05:41 UTC3 viewsread 13 August 2026

🚨Крымский район Абинский район Славянский район Меры безопасности! 🌐 Радар Юг | 📲 МЫ в MAX

Showing the 12 most recent of 20 posts we hold for @krd_alerts. 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.

Mentions

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“Krasnodar Alerts” (@krd_alerts), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/krd_alerts.

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.