Telegram RegisterThe public register of Telegram
Telegram profile photo for Коньково Контроль - КПРФ

Channel

Коньково Контроль - КПРФ

@konkovokontrol

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

363subscribers

-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-1001712304936
TypeChannel
Username@konkovokontrol
Created2 December 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live14 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/konkovokontrol

Topic

Politics & activism — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@konkovokontrol/7435 · this entry19 Jul 2026, 06:46 UTC@pervynarodnysovet/353119 Jul 2026, 06:47 UTC1.00under a minute
@pervynarodnysovet/353219 Jul 2026, 09:18 UTC@konkovokontrol/7436 · this entry19 Jul 2026, 16:01 UTC1.006.7 hours
@konkovokontrol/7438 · this entry23 Jul 2026, 12:24 UTC@pervynarodnysovet/353423 Jul 2026, 12:25 UTC1.002 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
@pervynarodnysovet10 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (9–1)

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. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 19 July 2026 to 31 July 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @konkovokontrol — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

3633673657 August 2026 — 367 subscribers8 August 2026 — 367 subscribers14 August 2026 — 366 subscribers22 August 2026 — 365 subscribers5 September 2026 — 364 subscribers13 September 2026 — 365 subscribers27 September 2026 — 366 subscribers7 October 2026 — 365 subscribers15 October 2026 — 366 subscribers29 October 2026 — 367 subscribers6 November 2026 — 366 subscribers14 November 2026 — 363 subscribers7 August 202614 November 2026
12 measurements spanning 100 days, net -4. 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 362–368 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Nov 2026, 19:59363-3
6 Nov 2026, 00:08366-1
29 Oct 2026, 19:11367+1
15 Oct 2026, 08:49366+1
7 Oct 2026, 07:17365-1
27 Sept 2026, 04:22366+1
13 Sept 2026, 17:22365+1
5 Sept 2026, 18:19364-1
22 Aug 2026, 04:48365-1
14 Aug 2026, 19:18366-1
8 Aug 2026, 04:08367no change
7 Aug 2026, 05:18367first reading

Engagement

12 posts held, back to 19 July 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 12 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

5 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 40.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁240.0%
❤120.0%
👎120.0%
🔥120.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 4 of the 12 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 19 July 2026 to 31 July 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

31 Jul 2026, 12:19 UTC36 viewsread 7 August 2026
Forwarded from @roditelimoskvynews

Говорящая голова Раковой врет и не краснеет https://t.me/depobr_mos/27404 , мы все прекрасно знаем как школьники «выбирают» продолжить обучение в колледже, когда их фактически выкидывают из школ после 9 класса, принуждая, чтобы учиться хоть где-то, а не тому, что интересно. Да, безусловно, часть детей добровольно и осознанно выбирают пойти в колледж, но подавляющему большинству чиновники в лице директоров школ с пода…

30 Jul 2026, 09:00 UTC34 viewsread 7 August 2026
Forwarded from @Condratenko_AEPhoto

Перед поездкой на родину стараюсь уменьшить накапливаемые долги. В прошедший понедельник, 20 июля, получил приглашение в ландшафтный заповедник "Теплый Стан", где у родника Холодный состоялся разговор с жителями Коньково и Теплого Стана. На фотографии - щит с информацией о уже несуществующих в столице особо охраняемых природных территориях. Основной темой беседы была тревога о настоящем и будущем зеленых легких Мос…

29 Jul 2026, 13:07 UTC35 views2 reactionsread 7 August 2026
Forwarded from @Condratenko_AEPhoto

Бенес Христофорович Айо пригласил в воскресенье, 5 июля, посетить с ним "белое пятно" в Донском районе. https://t.me/vosstanovleniesssr/36421 Место несколько загадочное своей незастроенностью практически в центре Москвы. Общение с работающими там прошло внешне вполне мирно и конструктивно. Но ответить хотя бы для себя на вопрос, готовится ли территория под застройку очередным ЖК или нет, не получилось. Увы, я забыл …

👎1🔥1

29 Jul 2026, 09:55 UTC52 viewsread 7 August 2026
Forwarded from @vera_ganzyaPhoto

Избили активиста, фиксирующего нарушения в Битцевском лесу 🔺 В продолжение темы о незаконных свалках на юге Москвы в районе Битцевского леса. Вчера избили нашего активиста, когда он пытался на одной из этих свалок снять на камеру телефона грузовик со строительным мусором. 🔺 Видно, серьёзные «братки» занимаются этим криминальным бизнесом. Вот теперь самое время узнать, почему эти свалки так долго живут и здравствуют…

27 Jul 2026, 19:01 UTC69 viewsread 7 August 2026
Forwarded from @msk1_newsVideo

Видео с Калужского шоссе, где произошла страшная авария 📸 «Новости Москвы»

26 Jul 2026, 10:08 UTC73 views0 reactionsread 7 August 2026
Forwarded from @msk1_news

Самосвал опрокинулся на 23-м км Калужского шоссе. Он полностью перекрыл туннель. ДТП случилось в районе Коммунарки, есть один пострадавший. Если вы были свидетелем произошедшего, присылайте видео нам: @news_msk1_bot 🟥 MSK1 в MAX | Прислать новость

25 Jul 2026, 04:56 UTC72 viewsread 7 August 2026
Forwarded from @uzaomsknewsVideo

😡 Угон «Газели» в Конькове раскрыли за несколько часов 🚨 Сотрудник компании оставил ключи в замке зажигания на ул. Введенского — машина тут же исчезла. Оперативники быстро вышли на 25-летнего иностранного студента. Он угнал авто в нетрезвом виде, устроил ДТП и бросил машину на Голубинской. ✏️ Возбуждено уголовное дело, фигурант под подпиской о невыезде. ЮЗАО Москва — подпишитесь, чтобы знать больше!

24 Jul 2026, 11:24 UTC79 viewsread 7 August 2026

Москва ⭐️ м. Беляево Ⓜ️ В caлон "Магия краcоты" по адресу ул. Профсоюзная 102А (тц Белка) тpебуeтся администратор салона💁🏻‍♀️ Условия: 1. График работы 2/2 с 10:00 до 22:00. Возможен индивидуальный график. 2. Заработная плата 2 раза в месяц. 3. Выход 4.000 + % за работу салона. 4. Есть зона отдыха и кухня. 5. Предоставляется скидка на услуги салона. При отклике просьба кратко рассказать о себе - возраст, опыт рабо…

23 Jul 2026, 12:24 UTC119 views2 reactionsread 7 August 2026
Photo

🤦‍♀️🧐Блестяще-безграмотная работа культурного (не побоимся этого слова!) отдела Префектуры ЮЗАО или Префектуры ЮЗАЮ Префектура ЮЗАО/ЮЗАЮ, вы кого «юзаете»? #префектураЮЗАО #префектураЮЗАЮ #мэр #мэрсобянин

😁2

20 Jul 2026, 12:33 UTC77 viewsread 7 August 2026
Forwarded from @vera_ganzyaPhoto

22 июля в 19:00 в Ясенево состоится встреча с депутатом Государственной Думы от фракции КПРФ Ольгой Николаевной Алимовой Это возможность для местных жителей рассказать о ситуации в районе и поднять темы, которые требуют внимания и конкретных действий. Собираемся на спортивной площадке за ТЦ «Этажи» — между домом 7 по Ясногорской улице и домом 13к1 по Новоясеневскому проспекту. 📆 22 июля 🕘 Начало в 19:00 Приходите…

19 Jul 2026, 16:01 UTC98 views1 reactionsread 7 August 2026

9️⃣1️⃣7️⃣ школьников выгнали с ЕГЭ за списывание. В этом году с экзаменов удалили 917 выпускников без права пересдачи. Они пытались списывать с помощью телефонов, микронаушников и других устройств. После этого Рособрнадзор предложил 🚫запретить продажу микронаушников. По словам главы ведомства Анзора Музаева, их почти не используют в быту — в основном покупают для списывания на экзаменах. 👆🚩У нас другое предложени…

❤1

19 Jul 2026, 06:46 UTC100 viewsread 7 August 2026

ГБУ «Жилищник района Коньково» сменило адрес ГБУ «Жилищник района Коньково» сообщает о смене местонахождения учреждения. Теперь организация располагается по новому адресу: город Москва, улица Миклухо-Маклая, дом 32, корпус 1.

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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.

Москва Новости
@msknews24 · 36,579
Telegram ranks this channel #65 of 96 here — alongside 95 others — read 2 October 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“Коньково Контроль - КПРФ” (@konkovokontrol), 363 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/konkovokontrol.

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.