Telegram RegisterThe public register of Telegram
Telegram profile photo for МЦУ - Анапа

Channel

МЦУ - Анапа

@mcuanapa

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

7,286subscribers

-85 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001413638194
TypeChannel
Username@mcuanapa
Created22 May 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live27 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/mcuanapa

Topic

Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.

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 word for word on 1 other registered channel. They sit inside a group of 4 channels that share the same post bodies with each other. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@mcuanapa/9547 · this entry4 Aug 2026, 14:22 UTC@anapa39kanal/239224 Aug 2026, 15:50 UTC1.0088 minutes
@anapa39kanal/239336 Aug 2026, 06:39 UTC@mcuanapa/9560 · this entry6 Aug 2026, 06:49 UTC1.0010 minutes
@mcuanapa/9558 · this entry6 Aug 2026, 06:33 UTC@anapa39kanal/239346 Aug 2026, 06:40 UTC1.007 minutes
@mcuanapa/9563 · this entry6 Aug 2026, 11:38 UTC@anapa39kanal/239396 Aug 2026, 19:28 UTC1.007.8 hours
@anapa39kanal/239417 Aug 2026, 06:33 UTC@mcuanapa/9570 · this entry7 Aug 2026, 06:39 UTC1.005 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@anapa39kanal5 (5/5 hand-verifiable sample passed)1.0010 minutesthis entry (3–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. 2 of the 2 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 28 comparable posts for this entry, running 4 August 2026 to 7 August 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).

Across the whole group of 4, the earliest publisher we hold is @mcuanapa — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

7,2867,3717,328.56 August 2026 — 7,371 subscribers6 August 2026 — 7,371 subscribers6 August 2026 — 7,370 subscribers9 August 2026 — 7,363 subscribers12 August 2026 — 7,362 subscribers15 August 2026 — 7,363 subscribers22 August 2026 — 7,357 subscribers25 August 2026 — 7,347 subscribers28 August 2026 — 7,338 subscribers1 September 2026 — 7,327 subscribers4 September 2026 — 7,320 subscribers10 September 2026 — 7,316 subscribers13 September 2026 — 7,310 subscribers18 September 2026 — 7,307 subscribers27 September 2026 — 7,286 subscribers6 August 202627 September 2026
15 measurements spanning 52 days, net -85. 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 7,273–7,384 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Sept 2026, 05:417,286-21
18 Sept 2026, 02:187,307-3
13 Sept 2026, 21:577,310-6
10 Sept 2026, 00:367,316-4
4 Sept 2026, 23:217,320-7
1 Sept 2026, 00:177,327-11
28 Aug 2026, 19:547,338-9
25 Aug 2026, 19:147,347-10
22 Aug 2026, 12:087,357-6
15 Aug 2026, 19:247,363+1
12 Aug 2026, 12:147,362-1
9 Aug 2026, 11:527,363-7
6 Aug 2026, 15:177,370-1
6 Aug 2026, 10:207,371no change
6 Aug 2026, 09:587,371first reading

Engagement

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

Reaction mix

305 reactions across 78 posts, in 10 distinct kinds. The most used accounts for 25.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎7725.2%
👍5618.4%
😁5217.0%
❤3411.1%
👌3310.8%
😱175.57%
🙏154.92%
🔥144.59%
👏61.97%
🎉10.328%

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 80 of the 94 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 305 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 94 most recent posts we hold, published 4 August 2026 to 20 August 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

20 Aug 2026, 08:27 UTC272 viewsread 20 August 2026
Photo

❗️Внимание, в Анапе введен временный запрет на использование надувных плавсредств. 🤓Сегодня, 20 августа в связи с отжимным ветром использование матрасов, кругов и других надувных плавательных средств запрещено. Управление гражданской обороны и защиты населения просит анапчан и гостей курорта быть осторожными, соблюдать меры личной безопасности, не подвергать неоправданному риску жизнь и здоровье!

20 Aug 2026, 06:58 UTC298 views6 reactionsread 20 August 2026
Forwarded from @anapaofficialPhoto

Информация о наличии топлива на АЗС Анапы Сегодня, 20 августа, по состоянию на 9:30 в городе-курорте работают 23 АЗС. На 10 АЗС по решению собственников введены ограничения – топливо отпускают только по топливным картам и для спецтранспорта. На 15 АЗС есть ограничения по отпуску топлива в баки по литражу (92 и 95 по 30 литров – на 6 АЗС; 92, 95 и ДТ по 40 литров – на 3 АЗС; ДТ по 50 литров – на 6 АЗС; ДТ по 60 литр…

👎6

20 Aug 2026, 06:24 UTC415 viewsread 20 August 2026
Photo

Внимание! ОТМЕНА СИГНАЛА «Угроза применения БПЛА». Опасности для жителей и гостей Анапы нет.

19 Aug 2026, 14:44 UTC429 views3 reactionsread 20 August 2026
Photo

Антитеррористическая комиссия напоминает: не прикасайтесь к бесхозным предметам Сумки, детские игрушки, электроника, кошельки, портмоне, купюры, оставленные в местах массового скопления людей, могут нести серьезную угрозу. При обнаружении бесхозных вещей необходимо: - ни в коем случае не допускать контакта с ними; - не использовать сотовую связь вблизи бесхозных предметов; - отойти на безопасное расстояние; - ув…

👍2😁1

19 Aug 2026, 13:44 UTC367 viewsread 20 August 2026
Forwarded from @anapaofficialPhoto

Внимание! ОТМЕНА СИГНАЛА «Атака БПЛА В АНАПЕ». Угроза применения беспилотников в Краснодарском крае пока сохраняется, ждите сигнал полной отмены. Единый телефон экстренных служб - 112.

19 Aug 2026, 12:18 UTC404 viewsread 20 August 2026
Photo

Внимание! Объявлена угроза атаки БПЛА При включении сирен-сигнала «Внимание всем» соблюдайте следующие правила Если вы дома: ✅Не выходите на улицу. Укройтесь в помещении без окон (ванная, туалет, коридор, кладовая) ✅Не пользуйтесь лифтом, держитесь подальше от окон и дверей Если вы на улице: ✅ Укройтесь в цокольном этаже ближайшего здания. Используйте для укрытия подвалы домов, подземные парковки. Опасно прятат…

19 Aug 2026, 06:57 UTC411 viewsread 20 August 2026
Forwarded from @anapaofficialPhoto

⚡️Внимание: экстренное предупреждение! По данным Краснодарского центра гидрометеорологии 19 и 20 августа местами на Кубани ожидается сильный дождь в сочетании с грозой, градом и усилением ветра с порывами до 22 м/с. Управление гражданской обороны и защиты населения предупреждает жителей и гостей курорта: будьте осторожны, соблюдайте меры личной безопасности, усильте контроль за детьми, при планировании поездок по к…

19 Aug 2026, 06:35 UTC425 views3 reactionsread 20 August 2026
Photo

Информация о наличии топлива на АЗС Анапы Сегодня, 19 августа, по состоянию на 9:30 в городе-курорте работают 22 АЗС. На 10 АЗС по решению собственников введены ограничения – топливо отпускают только по топливным картам и для спецтранспорта. На 10 АЗС есть ограничения по отпуску топлива в баки по литражу (92, 95 и 100 по 30 литров – на 6 АЗС; 92, 95 и ДТ по 40 литров – на 4 АЗС; ДТ по 50 литров – на 4 АЗС; ДТ по 60…

👎2😁1

19 Aug 2026, 06:34 UTC352 viewsread 20 August 2026
Forwarded from @anapaofficialPhoto

Внимание! ОТМЕНА СИГНАЛА «Угроза применения БПЛА». Опасности для жителей и гостей Анапы нет.

19 Aug 2026, 06:27 UTC434 views3 reactionsread 20 August 2026

❗️Уважаемые собственники и абоненты ПК «ОВ "ВЕТЕРАН"». В связи с засушливой погодой, большим разбором технической воды и сбоем в системе водоснабжения из-за скачков напряжения, на основании экстренного собрания Правления принято решение ввести временный график ограничения подачи тех.воды: 🗓с 19 по 21 августа 2026 г. (с возможной пролонгацией) с 11:00 до 17:00. 📍с. Супсех, ул. Фестивальная, Московская, Ленинградска…

😁2👎1

19 Aug 2026, 06:15 UTC414 views1 reactionsread 20 August 2026

❗️Внимание, работы будут производиться 25.08.2026 г.

👎1

18 Aug 2026, 14:29 UTC467 views2 reactionsread 20 August 2026
Forwarded from @anapaofficialPhoto

Внимание! Объявлена угроза атаки БПЛА При включении сирен-сигнала «Внимание всем» соблюдайте следующие правила Если вы дома: ✅Не выходите на улицу. Укройтесь в помещении без окон (ванная, туалет, коридор, кладовая) ✅Не пользуйтесь лифтом, держитесь подальше от окон и дверей Если вы на улице: ✅ Укройтесь в цокольном этаже ближайшего здания. Используйте для укрытия подвалы домов, подземные парковки. Опасно прятат…

😁2

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

@mcuanapa edited 1 post 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
12 August 2026
Most recent edit
12 August 2026

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

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.

🇷🇺ПВА
@pva_anapa · 94,901
Telegram ranks this channel #3 of 39 here — alongside 38 others — read 16 August 2026
🇷🇺 ЧП Анапа
@pva_chp · 93,924
Telegram ranks this channel #13 of 27 here — alongside 26 others — read 16 August 2026
Анапа Подслушано
@Anapad · 24,260
Telegram ranks this channel #17 of 78 here — alongside 77 others — read 23 September 2026
Юрий Озаровский Анапа Витязево Джемете
@MoreOz · 46,843
Telegram ranks this channel #24 of 88 here — alongside 87 others — read 26 August 2026
Анапа №1
@anapaa01 · 21,214
Telegram ranks this channel #32 of 66 here — alongside 65 others — read 24 September 2026
МАКОВОЗОВЫ
@makovozovy · 32,499
Telegram ranks this channel #32 of 88 here — alongside 87 others — read 5 September 2026

This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. 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 27 September 2026 — this entry's latest reading, not the date you are reading this.

“МЦУ - Анапа” (@mcuanapa), 7,286 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/mcuanapa.

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.