Telegram RegisterThe public register of Telegram

Channel

УК "Ресурсы Дома"

@Resdoma

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

288subscribers

+0 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-1001982070310
TypeChannel
Username@Resdoma
Descriptionг. Ногинск, ул. Комсомольская, д. 22а, офис 1. Телефон: 8 (496) 510-10-11, 8 (496) 510-10-12, 8 (929) 652-93-35
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/Resdoma

Growth

2887 Aug 2026, 23:14 — 288 subscribers8 Aug 2026, 08:18 — 288 subscribers7 Aug 2026, 23:148 Aug 2026, 08:18
2 measurements taken within a single day. 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 287–289 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 08:18288no change
7 Aug 2026, 23:14288first reading

Engagement

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

What this channel posts

Photos
287
Videos
14
Links
97

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.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍150.0%
🤬150.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 3 of the 18 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 5 March 2026 to 15 May 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

15 May 2026, 19:31 UTC224 views1 reactionsread 8 August 2026

АО «НПТО ЖКХ» 22:00 прекращена подача ГВС г. Ногинск ЦТП-31 Передано в АО «Мособлэнерго»

🤬1

16 Apr 2026, 17:18 UTC398 viewsread 8 August 2026

‼️Информацию узнали от жителей: 19:40 снижение параметров ГВС, ЦО, по некоторым адресам отсутствие от ЦТП-31 г. Ногинск ул. Комсомольская, д.18,20Б,22А,24 Информация направлена в АО "НПТО ЖКХ" для проведения мер по устранению инцидента

11 Apr 2026, 19:29 UTC513 views0 reactionsread 8 August 2026

22:20 прекращена подача ХВС г. Ногинск (весь город) Не включается ЭЭ на н/с в Молзино, после кратковременного отключения ЭЭ, электрик направлен Кто проводит работы выясняем Срок окончания работ не предоставлен

28 Mar 2026, 09:12 UTC602 viewsread 8 August 2026

Уважаемые жители дома 22а 4п, пожарная сигнализация сработала в кв.234.

27 Mar 2026, 16:07 UTC551 viewsread 8 August 2026
Photo

Уважаемые жители данных авто, вам необходимо в короткие сроки убрать свои авто , так как они мешают проезду спецтехники которая вывозит отходы.

26 Mar 2026, 12:24 UTC396 viewsread 8 August 2026

Уважаемые жители! Зафиксировано снижение параметров ГВС на вводе в дома 22А и 20 Б по ул.Комсомольская. Заявка передана в диспетчерскую службу.

20 Mar 2026, 07:29 UTC812 viewsread 8 August 2026

Уважаемые жители д.22 А ! Сегодня во 2 подъезде в кв. 138 в результате несанкционированных работ по электричеству произошло отключение ЭЭ по стояку. Ориентировочный срок подачи ЭЭ в 12 часов.

13 Mar 2026, 11:00 UTC555 viewsread 8 August 2026

Уважаемые жители дома 20Б ! Убедительная просьба не парковать свои автомобили возле 2-го подъезда . В этом подъезде проживает инвалид -колясочник, которому необходимо это пространство для беспрепятственного передвижения от дома до автомобиля.

13 Mar 2026, 05:35 UTC462 viewsread 8 August 2026

Осторожно: лёд опасен! Тёплая погода делает лёд на водоёмах обманчиво надёжным: сверху он может казаться твёрдым, но внутри уже рыхлый и разрушенный. Выходить на лёд сейчас — категорически нельзя! ⚠️Особенно опасно: -идти по льду в темноте или тумане; -собираться группами в одном месте; -выходить на лёд пьяным. Увидели, что кто‑то тонет? ✅Не бегите — ползите! ✅Бросьте палку, шарф или куртку. ✅Срочно звоните

12 Mar 2026, 07:59 UTC339 viewsread 8 August 2026

Уважаемые жители пожарная сигнализация сработала из за ремонтных работ в кв.132

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

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“УК "Ресурсы Дома"” (@Resdoma), 288 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Resdoma.

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.