Telegram RegisterThe public register of Telegram
Telegram profile photo for НВ 11 Новости

Channel

НВ 11 Новости

@sovetdomaNV11

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

269subscribers

-2 since we began measuring on 16 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002078827169
TypeChannel
Username@sovetdomaNV11
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live17 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 17 September 2026
On Telegramt.me/sovetdomaNV11

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 23 September 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.

Growth

26927127016 August 2026 — 271 subscribers17 August 2026 — 271 subscribers31 August 2026 — 270 subscribers9 September 2026 — 269 subscribers16 August 20269 September 2026
4 measurements spanning 23 days, net -2. 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 269–271 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 05:36269-1
31 Aug 2026, 10:36270-1
17 Aug 2026, 12:34271no change
16 Aug 2026, 20:45271first reading

Engagement

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

Reaction mix

52 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 34.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1834.6%
1528.8%
🤬611.5%
💯59.62%
🎉47.69%
👏23.85%
😢23.85%

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

Measured over the 14 most recent posts we hold, published 8 March 2026 to 27 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

27 Jul 2026, 09:14 UTC108 viewsread 16 August 2026
Forwarded from @Uprava_TroitskPhoto

Алексей Зотов проведет обход в микрорайоне «Центральный» Глава управы района Троицк совместно с жителями, своими заместителями, представителями ГБУ «Жилищник района Троицк», управляющей организации, муниципальными депутатами и общественными советниками в четверг, 30 июля, проведет еженедельный обход в жилом комплексе «Новые Ватутинки», мкрн «Центральный». ⌚Сбор участников состоится в 18:00 по адресу: р-н Троицк, Но

23 Jun 2026, 17:09 UTC229 viewsread 16 August 2026

Подача горячей воды завтра в первой половине дня.

9 Jun 2026, 09:43 UTC357 views2 reactionsread 16 August 2026

Уважаемые соседи, завтра, 10 июня, будет отключена горячая вода во всем доме с 10:00 до 12:00

😢2

4 Jun 2026, 15:42 UTC427 viewsread 16 August 2026

Бумажные КВИТАНЦИИ за май В ЯЩИКАХ

20 May 2026, 14:57 UTC720 viewsread 16 August 2026

Уважаемые соседи! Совет дома собирает информацию о протечке межпанельных швов для передачи в УК и создания заявки на выезд альпинистов. Если у вас в квартире есть проблема с подтеканиями на стыках панелей, то просьба сообщить информацию Старшему по дому @dmitry22sp в тг +7(906)7847828 в max, wa Просим вас указать в письме: - номер квартиры, подъезд, этаж; - номер телефона; - описание проблемного места (кухня, комнат

19 May 2026, 06:51 UTC427 views6 reactionsread 16 August 2026
Photo

Уважаемые соседи если у вас есть деньги на сигареты, то может и пепельницу себе преобретете или хотя бы банку Не бросайте бычки из окна. Это может привести к пожару.

💯51

19 May 2026, 06:49 UTC372 viewsread 16 August 2026

Внимание мошенники ‼️‼️‼️ Жителю нашего дома поступило сообщение от лица управляющей компании с требованием передать показания счетчиков. УК СпецКоммунПроект не рассылает подобные уведомления. Не сообщайте никому коды. Перезванивайте за уточнениями в бухгалтерию УК: +7(499)110-69-45 (доб.323)

9 May 2026, 16:37 UTC344 views12 reactionsread 16 August 2026
Forwarded from @spezkommunproektPhoto

Делимся атмосферой праздника с наших площадок. Именно из таких моментов и складывается настоящий День Победы- тёплый, живой и объединяющий. Спасибо всем, кто сегодня рядом с нами.

6👍6

5 May 2026, 12:58 UTC593 views4 reactionsread 16 August 2026
Photo

Приглашаем всех жителей дома и соседей из Новых Ватутинок в наш двор на празднование 9 мая!!! 🎉

🎉4

5 May 2026, 12:57 UTC228 views4 reactionsread 16 August 2026
Forwarded from @spezkommunproektPhoto

9 мая — особенный день для каждого из нас. Он про память, которая живёт в семьях. Про имена, которые нельзя забывать. Это день, когда прошлое становится ближе. Когда мы вспоминаем не только Победу, но и цену, которой она досталась. Приходите на праздник! Будем вместе — вспоминать, петь, угощать, улыбаться и благодарить. Ваша УК "СпецКоммунПроект"

👍4

5 May 2026, 12:56 UTC295 views1 reactionsread 16 August 2026

Бумажные КВИТАНЦИИ за апрель В ЯЩИКАХ

👍1

31 Mar 2026, 07:56 UTC336 views11 reactionsread 16 August 2026
Forwarded from @linervatutinkiPhoto

Завтра 01.04.2026 года в ТЦ Лайнер (Нововатутинский проспект д. 6) открывается Центр Госуслуг МФЦ Мои Документы. Добро пожаловать!

👍72👏2

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

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

Names

Channels on the register whose handles appear in this channel's posts.

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.

Ложка
@Lolojka · 93,083
Telegram ranks this channel #47 of 66 here — alongside 65 others — read 16 August 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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“НВ 11 Новости” (@sovetdomaNV11), 269 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/sovetdomaNV11.

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.