Channel
@zhilteploservis_puhovichi
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
152subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002299771723 |
|---|---|
| Type | Channel |
| Username | @zhilteploservis_puhovichi |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/zhilteploservis_puhovichi |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 17 Sept 2026, 12:17 | 152 | +4 |
| 8 Sept 2026, 15:39 | 148 | -1 |
| 30 Aug 2026, 21:07 | 149 | -1 |
| 23 Aug 2026, 20:19 | 150 | +2 |
| 15 Aug 2026, 19:26 | 148 | -2 |
| 8 Aug 2026, 19:47 | 150 | no change |
| 7 Aug 2026, 19:04 | 150 | first reading |
5 posts held, back to 4 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 5 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Работники УП «Жилтеплосервис» КХ оперативно ликвидируют последствия ночной грозы со шквалистым ветром в г.п. Руденск Пуховичского района. Важно отметить, что все службы работают в усиленном режиме, чтобы восстановить нормальное функционирование города как можно быстрее.
#5_РЕГИОН_ИТОГИ_2026 Итоги семи месяцев: коммунальная инфраструктура Минщины обновляется уверенными темпами Середина года - традиционное время подводить первые значимые промежуточные итоги. Для предприятий ЖКХ центрального региона этот период стал очередным этапом масштабной модернизации. Пока горожане пользуются горячей водой и уверенным напором в кранах, специалисты прокладывают под землёй современные инженерные …
🚧 Повышаем культуру безопасности: итоги областного семинара «День охраны труда» Сегодня состоялся практико-ориентированный семинар-учеба, приуроченный ко Дню охраны труда. Главная цель мероприятия - обмен передовым опытом и внедрение лучших практик в сфере безопасности на производстве. Участие в семинаре приняли начальник управления жилищного хозяйства АНДРЕЙ МАТЮХОВ и генеральный директор ГО "ЖКХ Минской области"…
#ZA_ЖКХ_В_ФАКТАХ 🧐С чего начиналось ЖКХ: дворники, ЖЭКи и «Доска позора» Истоки организованного городского благоустройства на Руси относятся к XVII веку. В 1649 году царь Алексей Михайлович издал указ «О градском благочинии», которым предписывалось содержать дворы в чистоте и назначать для этого специальных людей - дворников. ☝️ Таким образом, первых работников коммунальной сферы можно считать именно дворников. С…
🌾 Каравай Минщины уже во Дворце Независимости А сделала его мастерица из Молодечненского района. ✅ Подписаться на канал
Showing the 5 most recent of 5 posts we hold for @zhilteploservis_puhovichi. 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“ЖКХ Пуховщины” (@zhilteploservis_puhovichi), 152 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/zhilteploservis_puhovichi.
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.