Channel
@uklobnya
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Declared links · Cite this entry
1,566subscribers
-6 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001111086707 |
|---|---|
| Type | Channel |
| Username | @uklobnya |
| Created | Between 1 February 2017 and 31 October 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/uklobnya |
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 17 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 10:20 | 1,566 | -1 |
| 14 Sept 2026, 14:58 | 1,567 | -1 |
| 11 Sept 2026, 08:40 | 1,568 | -1 |
| 6 Sept 2026, 20:40 | 1,569 | +1 |
| 27 Aug 2026, 09:35 | 1,568 | -2 |
| 24 Aug 2026, 17:29 | 1,570 | +1 |
| 21 Aug 2026, 12:25 | 1,569 | -1 |
| 18 Aug 2026, 19:25 | 1,570 | -1 |
| 15 Aug 2026, 15:26 | 1,571 | -1 |
| 9 Aug 2026, 06:42 | 1,572 | no change |
| 8 Aug 2026, 11:03 | 1,572 | first reading |
4 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 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 4 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
16 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 93.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 15 | 93.8% | |
| 🤡 | 1 | 6.25% |
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 4 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 3 August 2026 to 5 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.
🔧 Подготовка к зиме: ремонт труб ЦО на ул. Юбилейная, 6 и ул. Ленина, 23, корп. 9 Уважаемые жители! В рамках подготовки многоквартирных домов к отопительному сезону наши специалисты провели ремонтные работы на трубопроводах системы центрального отопления (ЦО) по следующим адресам: ✅ Выполненные работы: ул. Юбилейная, д. 6 Ремонт труб ЦО ул. Ленина, д. 23, корп. 9 Ремонт труб ЦО 📌 Результат: Устранены изношенные участ…
👍4
🔧 Капитальный ремонт на ул. Ленина, д. 27: работы идут по графику! Уважаемые жители! Напоминаем, что в прошлом году на общем собрании собственников вы приняли решение о проведении капитального ремонта вашего дома. Благодаря вашему активному участию, Фонд капитального ремонта Московской области (ФКР) приступил к работам. ✅ Что уже сделано: Начат капитальный ремонт инженерных систем (замена сетей) Подрядчики выполняют …
👍3
Срочный ремонт кровли и фасада на ул. Мирная, д. 6 Уважаемые жители! Сообщаем о выполнении срочных ремонтных работ капитального характера по адресу: ул. Мирная, д. 6. Выполненные работы: ул. Мирная, д. 6 Ремонт кровли — более 900 м², устранение разрушений фасада Почему работы выполнены УК без решения ОСС? Собственники помещений в многоквартирном доме, систематически игнорируют вопросы своевременного капитального …
👍4🤡1
🔧 Привели в порядок входную группу на ул. Юбилейная, д. 6 Уважаемые жители! Сообщаем о выполнении работ по приведению ступеней входной группы в надлежащее состояние по адресу: ул. Юбилейная, д. 6. ✅ Что сделано: Восстановлены повреждённые участки ступеней Устранены сколы и неровности Обеспечена безопасность входа в подъезд Работы выполнены в рамках содержания общего имущества дома. 📞 Контакты: 📞 8 (499) 110-02-31 🤖 @…
👍4
Showing the 4 most recent of 4 posts we hold for @uklobnya. 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.
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.
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.
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.
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“УК Наш Дом Смарт” (@uklobnya), 1,566 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/uklobnya.
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.