Telegram RegisterThe public register of Telegram
Telegram profile photo for ЕДДС Краснодар

Channel

ЕДДС Краснодар

@eddskrd23

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

29,781subscribers

+757 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001619594356
TypeChannel
Username@eddskrd23
Created13 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/eddskrd23

Topic

Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 7 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@eddskrd23/11627 · this entry18 Oct 2026, 15:30 UTC@chpkrasnodara/8598818 Oct 2026, 15:31 UTC0.9872 seconds
@eddskrd23/11083 · this entry23 Aug 2026, 08:34 UTC@chpkrasnodara/8316923 Aug 2026, 09:20 UTC0.9846 minutes
@eddskrd23/11671 · this entry22 Oct 2026, 16:26 UTC@chpkrasnodara/8617622 Oct 2026, 17:01 UTC0.9835 minutes
@eddskrd23/11113 · this entry26 Aug 2026, 18:19 UTC@chpkrasnodara/8343626 Aug 2026, 18:20 UTC0.98under a minute
@eddskrd23/11734 · this entry28 Oct 2026, 13:37 UTC@chpkrasnodara/8641128 Oct 2026, 13:37 UTC0.98under a minute
@eddskrd23/11860 · this entry10 Nov 2026, 17:07 UTC@chpkrasnodara/8679810 Nov 2026, 17:14 UTC0.987 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@chpkrasnodara51 (8/8 hand-verifiable sample passed)0.985 minutesthis entry (51–0)
@mcu_krd45 (8/8 hand-verifiable sample passed)1.005 minutesthis entry (29–16)
@metalnikova_krasnodar9 (8/8 hand-verifiable sample passed)0.9711 minutesthis entry (8–1)
@fmr_krasnodar9 (8/8 hand-verifiable sample passed)1.003.0 hoursthis entry (8–1)
@KrasnodarUMR5 (5/5 hand-verifiable sample passed)1.0024 minutesthis entry (5–0)
@krdru22 (8/8 hand-verifiable sample passed)1.0038 minutes@krdru (12–10)
@bvk_mkr_vostochka8 (8/8 hand-verifiable sample passed)1.007 minutesthis entry (6–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 5 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 558 comparable posts for this entry, running 4 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the keys clone_mutual · clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

29,02429,78129,402.56 August 2026 — 29,024 subscribers7 August 2026 — 29,033 subscribers8 August 2026 — 29,062 subscribers8 August 2026 — 29,107 subscribers10 August 2026 — 29,162 subscribers11 August 2026 — 29,275 subscribers12 August 2026 — 29,290 subscribers13 August 2026 — 29,292 subscribers14 August 2026 — 29,299 subscribers16 August 2026 — 29,288 subscribers17 August 2026 — 29,304 subscribers18 August 2026 — 29,330 subscribers20 August 2026 — 29,327 subscribers21 August 2026 — 29,318 subscribers23 August 2026 — 29,311 subscribers24 August 2026 — 29,350 subscribers25 August 2026 — 29,363 subscribers27 August 2026 — 29,387 subscribers28 August 2026 — 29,422 subscribers28 August 2026 — 29,437 subscribers30 August 2026 — 29,438 subscribers1 September 2026 — 29,437 subscribers1 September 2026 — 29,436 subscribers2 September 2026 — 29,437 subscribers4 September 2026 — 29,431 subscribers6 September 2026 — 29,422 subscribers9 September 2026 — 29,450 subscribers12 September 2026 — 29,443 subscribers14 September 2026 — 29,451 subscribers17 September 2026 — 29,442 subscribers28 September 2026 — 29,431 subscribers5 October 2026 — 29,451 subscribers9 October 2026 — 29,474 subscribers13 October 2026 — 29,514 subscribers14 October 2026 — 29,525 subscribers15 October 2026 — 29,528 subscribers16 October 2026 — 29,521 subscribers17 October 2026 — 29,517 subscribers18 October 2026 — 29,508 subscribers19 October 2026 — 29,500 subscribers20 October 2026 — 29,513 subscribers22 October 2026 — 29,512 subscribers23 October 2026 — 29,517 subscribers24 October 2026 — 29,521 subscribers25 October 2026 — 29,537 subscribers26 October 2026 — 29,535 subscribers27 October 2026 — 29,561 subscribers28 October 2026 — 29,646 subscribers29 October 2026 — 29,647 subscribers30 October 2026 — 29,635 subscribers31 October 2026 — 29,644 subscribers1 November 2026 — 29,640 subscribers2 November 2026 — 29,646 subscribers3 November 2026 — 29,667 subscribers4 November 2026 — 29,683 subscribers6 November 2026 — 29,713 subscribers7 November 2026 — 29,722 subscribers8 November 2026 — 29,741 subscribers10 November 2026 — 29,761 subscribers12 November 2026 — 29,781 subscribers6 August 202612 November 2026
60 measurements spanning 98 days, net +757. 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 28,910–29,895 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
12 Nov 2026, 03:0029,781+20
10 Nov 2026, 02:4629,761+20
8 Nov 2026, 16:1929,741+19
7 Nov 2026, 07:5929,722+9
6 Nov 2026, 09:3629,713+30
4 Nov 2026, 13:4829,683+16
3 Nov 2026, 16:4729,667+21
2 Nov 2026, 16:4929,646+6
1 Nov 2026, 13:2029,640-4
31 Oct 2026, 11:5529,644+9
30 Oct 2026, 12:2929,635-12
29 Oct 2026, 10:1229,647+1
28 Oct 2026, 06:5129,646+85
27 Oct 2026, 04:0829,561+26
26 Oct 2026, 00:5629,535-2
25 Oct 2026, 01:0729,537+16
24 Oct 2026, 00:0529,521+4
23 Oct 2026, 00:4129,517+5
22 Oct 2026, 02:5129,512-1
20 Oct 2026, 19:2929,513first reading

Engagement

735 posts held, back to 3 August 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 163 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.22%
avg views ÷ 29,781 subscribers
Avg views / post
2,450
236 posts measured
Reaction rate
0.181%
reactions ÷ views · ER floor
Posts in window
236
of 735 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 232 of 236 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held735 (3 August 2026 – 11 November 2026)
Views total578,075
Reactions total1,035
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 00:15 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
11m 29s
Average length
20s

Measured directly from 34 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

3,404 reactions across 695 posts, in 19 distinct kinds. The most used accounts for 28.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤96028.2%
⚡74421.9%
😭3399.96%
🙏2336.84%
😁1915.61%
🤯1374.02%
🤔1313.85%
🎉1303.82%
👍1133.32%
😢1133.32%
😱982.88%
❤‍🔥641.88%
👀391.15%
👏320.94%
🔥250.734%
💘190.558%
💯140.411%
🥰130.382%
👌90.264%

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 715 of the 735 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 3,466 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 735 most recent posts we hold, published 3 August 2026 to 11 November 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

Telegram’s own ‘edited’ marker: 12 of 236 posts held from the last 30 days (5.08%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 20:16 UTC660 views1 reactionsread 12 November 2026

✅ Авария устранена. Все потребители запитаны.

❤1

11 Nov 2026, 19:51 UTC995 views2 reactionsread 12 November 2026
Photo

⚡ Произошло аварийное отключение электроэнергии в Карасунском округе Причина отключения – сработала защита на линии 6-10 кВ, отключены 25 трансформаторных подстанций. Без электроэнергии остались улицы: 📍 ул. Березовая 📍 ул. Богатырская 📍 ул. Виноградная 📍 ул. Гагарина 📍 ул. Енисейская 📍 ул. Заповедная 📍 ул. Картинная 📍 ул. Крайняя 📍 ул. Красивая 📍 ул. Новгородская 📍 ул. Ольховая 📍 ул. Первомайская 📍 ул. Платиновая…

⚡1❤1

11 Nov 2026, 15:13 UTC≈1,700 views3 reactionsread 12 November 2026
Photo

💡 Предупреждаем об отключении электроэнергии С 9:00 до 16:00 12 ноября и с 9:00 до 16:00 13 ноября не будет электричества по адресам: 📍ул. Генерала Трошева, 21, 25 📱 Дополнительную информацию можно уточнить в диспетчерской службе ООО "Югстрой-Электросеть" по тел. 238-40-06.

⚡1❤1🎉1

11 Nov 2026, 15:12 UTC≈1,610 views2 reactionsread 12 November 2026
Photo

💡 Предупреждаем об отключении электроэнергии 12 ноября С 9:00 до 18:00 не будет электричества по адресам: 📍ул. Заполярная, 39, корп. 7, 9, стр. 2, стр. 5 📱 Дополнительную информацию можно уточнить в диспетчерской службе ООО «ЭКСТЕХ» по тел. 205-00-51.

⚡1❤1

11 Nov 2026, 15:12 UTC≈1,250 views1 reactionsread 12 November 2026
Photo

💡 Предупреждаем об отключении электроэнергии 12 ноября х. Ленина С 8:00 до 19:00 не будет электричества по адресам: 📍 ул. Буковая, 2, 4, 6, 8 📍 пер. Буковый, 2, 4, 6, 8, 8, 12, 14, 16, 18, 20, 22, 24, 24а, 26, 28, 28а, 30, 32 📍 ул. Наримановская, 28, 40, 42, 44, 48, 50, 52 📍 ул. Стременная, 2/2 📱 Дополнительную информацию можно уточнить в диспетчерской службе ООО "Югстрой-Электросеть" по тел. 238-40-06.

⚡1

11 Nov 2026, 15:12 UTC≈1,180 viewsread 12 November 2026
Photo

💧 Предупреждаем об отключении водоснабжения С 9:00 до 17:00 будет отключено водоснабжение по адресам: 📍ул. Кореновская, 48 📍ул. Ярославская, 128 📱 Дополнительную информацию можно уточнить в диспетчерской службе ООО «Краснодар Водоканал» по тел. 220-28-38, 217-03-33.

11 Nov 2026, 15:12 UTC≈1,090 viewsread 12 November 2026
Photo

💦 Предупреждаем о снижении давления водоснабжения 12 ноября С 9:00 до 17:00 будет снижено давление водоснабжения по адресам: 📍ул. Ленина, 97 📍ул. Суворова, 50 📱 Дополнительную информацию можно уточнить в диспетчерской службе ООО «Краснодар Водоканал» по тел. 220-28-38, 217-03-33.

11 Nov 2026, 15:11 UTC≈1,350 views4 reactionsread 12 November 2026
Photo

💡 Предупреждаем об отключении электроэнергии 12 ноября С 8:00 до 17:00 не будет электричества по адресам: 📍ул. Березовая, 1–15, 6–22, 19–23, 24–30 📍ул. Бригадная 📍ул. Васюринская, 2–30, 3–25 📍ул. Виноградная, 2–16, 1–15, 19–43, 22–34 📍ул. Дзержинского, 98, 116/7, 118 📍ул. Жемчужная, 2–24, 3–25 📍ул. Задунайская, 59 📍ул. Игнатова, 51, 53, 57 📍ул. Коллективная 📍ул. Курганная, 4–14, 5–17 📍пер. Курганный 📍ул. Лесопарков…

❤2⚡1👍1

11 Nov 2026, 12:12 UTC≈2,340 views4 reactionsread 12 November 2026
Photo

☔ Штормовое предупреждение! С 12 по 13 ноября местами по Краснодарскому краю ожидается комплекс метеорологических явлений: сильный дождь в сочетании с порывами ветра до 20–25 м/с. 📱 В случае возникновения чрезвычайных ситуаций звонить по Единому номеру вызова экстренных служб – «112».

⚡2❤1🎉1

11 Nov 2026, 12:06 UTC≈1,910 views9 reactionsread 12 November 2026

Заместитель главы Краснодара Анна Леонова рассказала, как действовать при объявлении сигнала «Внимание всем!» Уважаемые родители, чтобы у каждой семьи было четкое понимание порядка действий, подготовили памятку с основными ситуациями и рекомендациями. 1. Сигнал «Внимание всем!» объявлен ночью или утром, до начала занятий в школе или детском саду. Если сигнал поступил до выхода ребенка из дома, рекомендуем оставить…

👍4😁3❤1🙏1

11 Nov 2026, 04:30 UTC≈2,790 views7 reactionsread 12 November 2026

❕Школы и детские сады Краснодара работают в соответствии с расписанием Уважаемые родители, если вы решили не направлять сегодня ребёнка в детский сад или школу, то пропуск будет считаться по уважительной причине. Проинформируйте о принятом решении воспитателя или классного руководителя. 📱 Телеграм 📱 ВК 📲 MAX

❤5⚡1😁1

11 Nov 2026, 04:30 UTC≈2,790 views3 reactionsread 12 November 2026
Photo

Отмена сигнала «Беспилотная опасность». 🔵 Если вы обнаружили обломки беспилотника: сообщите об этом по телефону 112, не подходите и по возможности не допускайте к ним третьих лиц до прибытия правоохранительных органов и спецслужб, не фотографируйте. 🔵 При обнаружении публикаций об этом в соцсетях и мессенджерах — не отвечайте на уточняющие вопросы в комментариях. 📱 Телеграм 📱 ВК 📲 MAX

❤2😁1

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

Posts edited after publishing

@eddskrd23 edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
18 August 2026
Most recent edit
31 October 2026

Posts recorded as deleted after publishing

We recorded 1 post on @eddskrd23 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
4 October 2026
Most recent seen missing
4 October 2026
Median time before seen missing
30 hours
Seen missing in the last 30 days
0

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 6 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Типичный Краснодар
@krd_tipich_ru · 377,884
#1
МЦУ Краснодар
@mcu_krd · 21,386
#2
Туподар ♥️ Краснодар
@typodar · 56,554
#3
KRD.ru
@krdru · 19,891
#4
МЧС Краснодарского края
@mchs_kuban · 7,120
#5
Дептранс Краснодара
@deptrans_krd · 4,785
#6
Краснодарские известия
@ki_krd · 14,995
#7
Кубань 24
@kuban24 · 129,144
#8
93.RU | Новости Краснодара и края
@news_93_ru · 27,840
#9
Краснодар и край
@krasnodarkray1 · 187,176
#10
Телеканал «Краснодар»
@mtrk_krasnodar · 16,911
#11
ЧП Краснодар™
@chp_krd · 89,553
#12
МАКСИМ ОНИЩЕНКО | Замглавы Краснодара
@zhkhkrasnodar · 842
#13
Оперативный штаб - Краснодарский край
@opershtab23 · 51,572
#14
Россия. Кубань | Новости
@russiakuban · 45,245
#15
ЧП Краснодара и края 🔞
@chpkrasnodara · 290,270
#16
Вениамин Кондратьев
@kondratyevvi · 58,508
#17
Блокнот Краснодар
@bloknotkrasnodar · 27,903
#18
Жесть Краснодара и Края
@ghestkrd · 107,373
#19
Кубанские Инсайды
@dedmazai911 · 18,176
#20
КРАСНОДАРСКИЕ ЭЛЕКТРОСЕТИ
@rosseti_kuban_krasnodarseti · 9,839
#21
Краснодар ДТП и ЧП | КРДДТП | Авто новости Кубани
@krddtp1 · 43,026
#22
ЛАВРЕНТЬЕВ 18+
@Lavrentiev_PA · 738
#23
Кубань 2️⃣3️⃣ Краснодар
@kuban_23 · 76,046
#24
Министерство ГО и ЧС КК
@mingochskk · 1,821
#25
МЧС Республики Адыгея
@mchs0101 · 2,443
#26
Утренний Юг | Новости Краснодара и края
@UtrennijYug · 4,487
#27
Департамент городского хозяйства и ТЭК
@dghkrd · 1,342
#28
Югополис - Новости Краснодара и края
@yugopolis · 3,920
#29
Соцвопросы Краснодар
@soc_voprocy_krd · 976
#30
Краснодар Новости Bigbro_krd
@bigbro_krd · 32,073
#31
Посёлок Российский Краснодар
@posroskrd · 4,821
#32
КРАСНОДАР новости - ЮГ-24
@yug_24_ru · 139,708
#33
Карасунский округ Краснодара
@karasuninfo · 4,668
#34
Сельхоз ЮМР Краснодар
@selhoz_umr_krasnodar · 2,935
#35
Краснодар | Телетайп
@tipichkras · 124,123
#36
Сарказм Помидоррова in Deutschland
@fotozhaba · 5,209
#37
Полиция Краснодара
@mvd23krasnodar · 6,728
#38
МУП «КТТУ»
@kttukrd · 10,458
#39
VOKRYG ROSSINSKOGO
@vokryg_rossinskogo · 11,955
#40
Евгений Наумов
@emnaumov · 17,685
#41
Прокуратура Краснодарского края
@proc_23 · 9,715
#42
Госавтоинспекция Кубани
@gibdd123region · 10,398
#43
Прикубанский округ Краснодара
@prikubanka_krd · 9,324
#44
РБК Краснодар
@rbc_krasnodar · 5,855
#45
Коммерсантъ Кубань-Черноморье
@kommersant_kuban · 5,137
#46
Администрация Краснодарского края
@admkrai · 12,112
#47
СУ СКР по Краснодарскому краю
@kubansledcom · 10,321
#48
Кубанские Новости
@kub_news_ru · 42,144
#49
23 МВД
@mvd_23 · 18,991
#50
Юга.ру
@yugaru · 4,844
#51
Депстрой Краснодара
@depstroy23 · 1,514
#52
Анна Минькова
@minkovaanna23 · 4,449
#53
КП-Кубань. Новости Краснодара и края
@kp_kuban · 11,719
#54
Новый трамвай Краснодара
@krasnodar_tram · 2,362
#55
Краснодарские парки
@KrasnodarskieParki · 2,996
#56
Краснодар ЮМР
@KrasnodarUMR · 9,484
#57
Краснодача
@krasnodach · 4,773
#58
Typicalkrd | Типичный Краснодар (и край!)
@ttypicalkrd · 8,046
#59
Живая Кубань
@live_kuban · 26,763
#60
Шанхай Краснодар
@shanhai_krasnodar · 15,543
#61
ЮРПСО МЧС России
@urpso_mchs · 1,667
#62
Фестивальный Краснодар ♥️
@fmr_krasnodar · 9,418
#63
Полиция Сочи
@police_sochi · 5,062
#64
Костя Таксист
@kostyaelvis · 4,071
#65
Росгвардия Краснодарский край
@rosgvard_krasnodar · 2,112
#66
#GMRLIVE
@gmrlive · 15,575
#67
Администрация МО город-герой Новороссийск
@nvrskadm · 9,622
#68
Туристско-информационный центр г. Краснодара
@tickrasnodar · 1,803
#69
Служба спасения Сочи
@spasenie_sochi · 518
#70
🇷🇺 ОБЩЕСТВЕННЫЙ ТРАНСПОРТ КРАСНОДАРА 🇷🇺
@krasnodar_transport · 1,657
#71
Центральный округ Краснодара
@infocenter_krd · 1,670
#72
МКР Любимово
@gk_lyubimovo · 11,233
#73
Кубанéц - свободная энциклопедия Краснодарского края
@kubanec · 1,339
#74
Микрорайон Метальникова
@metalnikova_krasnodar · 6,851
#75
Спортивный Краснодар
@dfks_krasnodar · 1,466
#76
Фёдор Бабенков | Темрюкский район
@FedorBabenkov · 2,903
#77
Западный округ Краснодара
@azvo_krd · 1,326
#78
Геленджик | Пресс-служба администрации
@adm_gelen · 6,331
#79
Типичный Краснодар
@krd_tipich · 26,868
#80
Евгений Первышов
@PervyshovEA · 14,879
#81
Мэрия Анапы
@anapaofficial · 17,174
#82
Восточка ККБ Краснодар
@bvk_mkr_vostochka · 12,493
#83
КРАСНОДАРСКОЕ БЕЗУМИЕ
@krd_madness · 846
#84
Поселок Российский | Краснодар
@rossiyskiyobyavleniya · 8,384
#85
Департамент образования МО г.Краснодар
@dokrdru · 2,462
#86
ФК «Краснодар»
@fckrasnodar · 111,482
#87
Kub Mash
@kub_mash · 113,013
#88
Объединенная пресс-служба судов Краснодарского края
@opskuban · 5,567
#89
tuapseregion
@tuapseregionadm · 3,402
#90
Южная транспортная прокуратура
@prokutp · 3,090
#91
Кубанская журналистика (tm)
@kubzhur · 674
#92

Read from Telegram’s recommendation API, most recently 8 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

МЦУ Краснодар
@mcu_krd · 21,386
Telegram ranks this channel #3 of 95 here — alongside 94 others — read 23 September 2026
Типичный Краснодар
@krd_tipich_ru · 377,884
Telegram ranks this channel #16 of 81 here — alongside 80 others — read 10 August 2026
Туподар ♥️ Краснодар
@typodar · 56,554
Telegram ranks this channel #18 of 94 here — alongside 93 others — read 23 August 2026
KRD.ru
@krdru · 19,891
Telegram ranks this channel #19 of 94 here — alongside 93 others — read 30 September 2026
Краснодар ДТП и ЧП | КРДДТП | Авто новости Кубани
@krddtp1 · 43,026
Telegram ranks this channel #19 of 93 here — alongside 92 others — read 28 August 2026
93.RU | Новости Краснодара и края
@news_93_ru · 27,840
Telegram ranks this channel #20 of 95 here — alongside 94 others — read 10 September 2026
Оперативный штаб - Краснодарский край
@opershtab23 · 51,572
Telegram ranks this channel #25 of 90 here — alongside 89 others — read 24 August 2026
ЧП Краснодара и края 🔞
@chpkrasnodara · 290,270
Telegram ranks this channel #28 of 89 here — alongside 88 others — read 10 August 2026
Жесть Краснодара и Края
@ghestkrd · 107,373
Telegram ranks this channel #30 of 94 here — alongside 93 others — read 14 August 2026
ЧП Краснодар™
@chp_krd · 89,553
Telegram ranks this channel #35 of 94 here — alongside 93 others — read 17 August 2026
Блокнот Краснодар
@bloknotkrasnodar · 27,903
Telegram ranks this channel #37 of 99 here — alongside 98 others — read 11 September 2026
Кубань 24
@kuban24 · 129,144
Telegram ranks this channel #39 of 90 here — alongside 89 others — read 13 August 2026
НОВОСТИ Краснодара и Края
@vesti_krd · 20,193
Telegram ranks this channel #41 of 86 here — alongside 85 others — read 28 September 2026
Новости Краснодара | Сочи Анапа
@krasnodar1 · 30,922
Telegram ranks this channel #43 of 90 here — alongside 89 others — read 5 September 2026
Россия. Кубань | Новости
@russiakuban · 45,245
Telegram ranks this channel #44 of 92 here — alongside 91 others — read 27 August 2026
Вениамин Кондратьев
@kondratyevvi · 58,508
Telegram ranks this channel #45 of 93 here — alongside 92 others — read 22 August 2026
Краснодар и край
@krasnodarkray1 · 187,176
Telegram ranks this channel #46 of 93 here — alongside 92 others — read 11 August 2026
Краснодар Новости Bigbro_krd
@bigbro_krd · 32,073
Telegram ranks this channel #47 of 92 here — alongside 91 others — read 4 September 2026
Кубань 2️⃣3️⃣ Краснодар
@kuban_23 · 76,046
Telegram ranks this channel #49 of 95 here — alongside 94 others — read 19 August 2026
КРАСНОДАР новости - ЮГ-24
@yug_24_ru · 139,708
Telegram ranks this channel #50 of 93 here — alongside 92 others — read 13 August 2026
Евгений Наумов
@emnaumov · 17,685
Telegram ranks this channel #51 of 93 here — alongside 92 others — read 4 October 2026
Твой Краснодар
@tvoi_krd · 68,800
Telegram ranks this channel #55 of 90 here — alongside 89 others — read 20 August 2026
23 МВД
@mvd_23 · 18,991
Telegram ranks this channel #58 of 93 here — alongside 92 others — read 3 October 2026
Парк Галицкого Краснодар
@park_galitskogo · 49,812
Telegram ranks this channel #60 of 96 here — alongside 95 others — read 25 August 2026

This channel appears in 37 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“ЕДДС Краснодар” (@eddskrd23), 29,781 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/eddskrd23.

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.