Channel
@ukomunity
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
967subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002133015084 |
|---|---|
| Type | Channel |
| Username | @ukomunity |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ukomunity |
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 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 why it has no browse page of its own yet.
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.
Posts published here appear word for word on 1 other registered channel. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @zhkdok1/49124 Apr 2026, 07:23 UTC | @ukomunity/590 · this entry24 Apr 2026, 07:23 UTC | 1.00 | under a minute |
| @zhkdok1/4935 May 2026, 10:34 UTC | @ukomunity/591 · this entry5 May 2026, 10:35 UTC | 1.00 | 72 seconds |
| @zhkdok1/4945 May 2026, 10:34 UTC | @ukomunity/592 · this entry5 May 2026, 10:35 UTC | 1.00 | under a minute |
| @zhkdok1/49925 May 2026, 07:17 UTC | @ukomunity/597 · this entry25 May 2026, 07:17 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @zhkdok1 | 11 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @zhkdok1 (11–0) |
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 5 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 16 comparable posts for this entry, running 14 April 2026 to 1 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.
Across the whole group of 2, the earliest publisher we hold is @zhkdok1. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 8 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 00:47 | 967 | no change |
| 7 Aug 2026, 13:32 | 967 | first reading |
20 posts held, back to 14 April 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 20 posts for this entry, the most recent from 1 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 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.
47 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 59.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 28 | 59.6% | |
| ❤ | 10 | 21.3% | |
| 👎 | 7 | 14.9% | |
| 😁 | 2 | 4.26% |
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 13 of the 20 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 47reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 14 April 2026 to 1 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.
Уважаемые собственники квартир Краснооктябрьской 8 У вас образовалась задолженность (долг и текущий платеж) за коммунальные услуги, которую необходимо погасить! Напоминаем, что квартплату необходимо оплачивать ежемесячно до 20 числа в соответствии с п.1 ст. 153 ЖК РФ и 354 постановлением п.66, граждане и организации обязаны своевременно и полностью вносить плату за жилое помещение и коммунальные услуги. При неопла…
❤2😁2👍1
📢 ИНФОРМАЦИОННОЕ СООБЩЕНИЕ Уважаемые собственники помещений многоквартирных домов №6 и №8 по ул. Краснооктябрьская! Информируем вас о проведении информационного собрания с представителями управляющей компании. 📅 Дата и время проведения: Четверг 02 июля 2026 года в 18:30 Место проведения: Офис управляющей компании ООО «Комьюнити» г. Тюмень, ул. Краснооктябрьская, д.8 строение 1, (здание отдела продаж) На собрании вы …
⚡️Уважаемые жители! ИНФОРМАЦИЯ ОБ ОТКЛЮЧЕНИИ ЭЛЕКТРОЭНЕРГИИ⚡️ В связи с проведением работ по замене трансформаторов тока во вводно-распределительном устройстве (ВРУ-0,4кВ) будет произведено поэтапное отключение электроэнергии. Важно! Отключение будет: * Кратковременным * Поэтапным (не весь дом сразу) * В пределах указанного временного интервала Адрес: ул. Краснооктябрьская, дом 8 Период проведения работ: 25 июня 20…
❤1
🔔 🔔🔔 Не забудьте, пожалуйста, передать показания счетчиков до 25-го числа. 🔔🔔🔔
Уважаемые жители! Информируем вас о временном отключении горячего водоснабжения по адресу: ул. Краснооктябрьская, д. 8. Дата проведения работ: 28 мая 2026 года (среда).Время отключения: с 10:00 до 13:00. В указанный период будут проводиться необходимые технические работы. Подача горячей воды будет возобновлена ориентировочно к 13:00. Приносим извинения за доставленные неудобства.
Уважаемые жители ЖК «ДОК»! Информируем вас о поступающих в управляющую компанию многочисленных жалобах от жителей дома на нарушение режима тишины во дворе. В ночное время (после 23:00) на детских площадках и во дворе дома фиксируются следующие нарушения: • Игра в футбол и другие активные игры с мячом • Катание на самокатах и скейтбордах • Громкие крики и шумные игры Напоминаем, что согласно законодательству …
👍2
В случае продолжения нарушений жильцы дома будут вынуждены: • Вызывать сотрудников полиции • Принимать меры административного воздействия • Обращаться в правоохранительные органы Давайте вместе создадим комфортную и безопасную среду проживания для всех жителей дома! С уважением, Управляющая компания «Комьюнити»
❤2
📢 Уважаемые жители❗️ Информируем вас о проведении ремонтных работ резинового покрытия на придомовой территории нашего дома. Сегодня в течение дня специалисты будут производить ремонт покрытия во дворе. Важная просьба: Объясните детям, что нельзя наступать на свежеуложенное покрытие Следите за тем, чтобы дети не играли на отремонтированных участках Проконтролируйте поведение детей во время проведения работ Обратите вн…
👍2❤1
Уважаемые жители! Наступил долгожданный летний сезон, и многие из вас устанавливают кондиционеры для создания комфортной температуры в квартирах. Однако важно помнить, что ваш комфорт не должен создавать дискомфорт для соседей. Проблема конденсата от кондиционеров становится особенно актуальной в жаркие дни. Капающая вода не только портит внешний вид фасада здания, но и создаёт постоянный шум, нарушающий покой жиль…
👍2
Помните: - Неправильно организованный отвод конденсата может повредить фасад дома - Постоянный стук капель мешает отдыху соседей - Нарушение правил установки влечёт административную ответственность Проявляя уважение к соседям, вы помогаете создать комфортную атмосферу для всех жителей дома. Предлагаем каждому владельцу кондиционера проверить правильность организации дренажной системы и при необходимости провести её …
🔔 🔔🔔 Не забудьте, пожалуйста, передать показания счетчиков до 25-го числа. 🔔🔔🔔
Уважаемые собственники квартир Краснооктябрьской 8 У вас образовалась задолженность (долг и текущий платеж) за коммунальные услуги, которую необходимо погасить! Напоминаем, что квартплату необходимо оплачивать ежемесячно до 20 числа в соответствии с п.1 ст. 153 ЖК РФ и 354 постановлением п.66, граждане и организации обязаны своевременно и полностью вносить плату за жилое помещение и коммунальные услуги. При неопла…
❤3👎1
Showing the 12 most recent of 20 posts we hold for @ukomunity. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“ЖК DOK Краснооктябрьская д.8” (@ukomunity), 967 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ukomunity.
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.