Telegram RegisterThe public register of Telegram

Channel

ЧаВо по ЖКХ | ТСЖ, УК, ЖСК и жителям

@gkhfaq

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

431subscribers

-1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001202987203
TypeChannel
Username@gkhfaq
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 6 August 2026
On Telegramt.me/gkhfaq

Topic

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 59% 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.

Observations

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.

Content that also appears on other registered channels

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.

Matching posts — open both and compare (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@sovetmkd/6030 Mar 2026, 07:27 UTC@gkhfaq/113 · this entry30 Mar 2026, 07:27 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@sovetmkd5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (50)

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 0 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 20 comparable posts for this entry, running 2 June 2022 to 16 April 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @gkhfaq — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 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.

Also posting the same content

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.

Growth

431432431.56 Aug 2026, 12:46 — 432 subscribers6 Aug 2026, 19:19 — 432 subscribers6 Aug 2026, 23:55 — 431 subscribers6 Aug 2026, 12:466 Aug 2026, 23:55
3 measurements taken within a single day, net -1. 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 431–432 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 23:55431-1
6 Aug 2026, 19:19432no change
6 Aug 2026, 12:46432first reading

Engagement

20 posts held, back to 2 June 2022the 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 16 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

16 Apr 2026, 07:32 UTC99 viewsread 6 August 2026
Forwarded from @gkhvsemFile

☺️ Напоминаю про памятку по количеству голосов на общем собрании собственников — Вопросы разбиты по темам, что гораздо удобнее распространенной разбивки по количеству голосов. — Добавлены ссылки на статьи, которые могут быть полезны при проведении собрания. — В самом начале памятки есть ссылка на страницу ЖКХ Ньюс, где всегда сможете найти последнюю версию документа. Ссылку на ДомОнлайн, в котором можно оформить в

3 Apr 2026, 06:18 UTC126 viewsread 6 August 2026
Forwarded from @gkhvsem

😎 25+ документов в помощь инициатору собрания Весна — традиционная «жара» для годовых общих собраний собственников. Чтобы сэкономить ваше время, собрала подборку актуальных шаблонов. Это документы из модуля учредителя ЖКХ Ньюс — сервиса ДомОнлайн, которые помогут закрыть бюрократические вопросы. ✉️ Самое сложное — правильно начать. Тут пригодятся: — Сообщение о собрании (стандартное, табличное и даже «понятное») —

30 Mar 2026, 07:27 UTC114 viewsread 6 August 2026

💎 Общее собрание собственников: руководство по переговорам для набора кворума Почему один инициатор собирает кворум за несколько вечеров, а другой месяц обивает пороги без результата? Секрет не в магии, а в подготовке. Прежде чем позвонить по телефону или в дверь, нужно знать не только номер квартиры, но и «ключ» к её владельцу. «Скептик» боится обмана, «Буквоед» ищет нарушения в процедуре, а «Пассивный обыватель»

20 Mar 2026, 05:14 UTC112 viewsread 6 August 2026
Forwarded from @gkhvsemFile

❗️Протокол по новым правилам 2025 года (по приказу Минстроя №266/пр) Накануне проведения годовых собраний дублирую шаблоны документов по новым требованиям, которые вступили в силу с 1 сентября 2025 года. К посту прикрепляю основную часть — протокол, а по ссылкам ниже можно скачать все остальное. ❗️ Приложение: «Сведения о лицах, участвующих в собрании» 📨 Другие документы, которые составляются в ходе собрания и до

13 Mar 2026, 05:45 UTC140 viewsread 6 August 2026
Forwarded from @gkhvsem

🌷 Скоро второй квартал — традиционное время для проведения годовых собраний. Подписчикам из числа активных собственников, советов МКД по-прежнему рекомендую воспользоваться недорогим сервисом ДомОнлайн для подготовки документов. Инициатор сможет: ▪️получить с нуля или перепроверить имеющиеся данные о площадях в доме, чтобы не было ошибок при подсчете голосов; ▪️автоматически сформировать документы к собранию, включ

26 Feb 2026, 03:36 UTC169 viewsread 6 August 2026

📚 Как провести общее собрание собственников в очно-заочной форме: 9 шагов и 20 образцов документов Накануне проведения годовых собраний публикуем наш путеводитель для проведения общего собрания собственников (ОСС) — по шагам и с образцами документов. 1⃣ Подготовка к собранию. Инициатор ▪️Кто может быть инициатором собрания ▪️К чему приводит указание в качестве инициатора собрания “совета МКД” ▪️Как инициатору уведо

18 Feb 2026, 05:41 UTC157 viewsread 6 August 2026
Forwarded from @gkhvsemFile

❗️Протокол по новым правилам 2025 года (по приказу Минстроя №266/пр) Накануне проведения годовых собраний дублирую шаблоны документов по новым требованиям, которые вступили в силу с 1 сентября 2025 года. К посту прикрепляю основную часть — протокол, а по ссылкам ниже можно скачать все остальное. ❗️ Приложение: «Сведения о лицах, участвующих в собрании» 📨 Другие документы, которые составляются в ходе собрания и до

18 Dec 2025, 06:01 UTC294 viewsread 6 August 2026

❗️Запасные каналы о ЖКХ в MAХ — для тех, у кого Telegram работает только через Wi-Fi — подпишитесь на наши каналы в альтернативном мессенджере: ➡ ЖКХ Ньюс - https://max.ru/gkhnews ➡ ЖКХ - https://max.ru/gkhvsem

3 Dec 2025, 05:48 UTC356 viewsread 6 August 2026
Forwarded from @gkhvsem

✨ Оспаривание решений собрания: путеводитель по теме Ранее публиковала пошаговую инструкцию, как провести собрание. Теперь собрала в одном месте публикации про оспаривание решений собрания. С чего начать + отдельные тактические приёмы ▪️Обязательный чек-лист перед обращением в суд 📄 Образец сообщения от собственника о намерении обратиться в суд с заявлением о признании решений общего собрания собственников недейст

26 Nov 2025, 15:35 UTC211 viewsread 6 August 2026
Forwarded from @gkhvsem

✅ Библиотека собственника: 50+ инструкций по всем вопросам ЖКХ сборник самых полезных материалов канала и сайта, который будет удобной настольной книгой для собственника ❓ РАЗДЕЛ 1: Как узнать и найти (справочная информация) Как узнать... — Включён ли дом в программу капремонта — Как найти хорошую управляющую компанию — Признан ли дом аварийным — Как и где искать судебную практику по ЖКХ — Как узнать, вынесен ли в

26 Nov 2025, 15:33 UTC140 viewsread 6 August 2026
Forwarded from @gkhvsem

😎 БИБЛИОТЕКА УПРАВЛЯЮЩЕЙ КОМПАНИИ: 60+ инструкций по правовым и практическим вопросам управления МКД Сборник самых полезных материалов для специалистов УК, который станет настольной книгой по юридическим, финансовым и техническим аспектам работы с многоквартирными домами. 📄 РАЗДЕЛ 1: Договорная работа и отношения с собственниками Договор управления: — Какие условия ущемляют права потребителя, и их нельзя включать

26 Nov 2025, 15:33 UTC136 viewsread 6 August 2026
Forwarded from @gkhvsem

библиотека управляющей организации — продолжение (начало ⬆️) 🏬 РАЗДЕЛ 5: Технические вопросы и эксплуатация МКД Отопление и водоснабжение: — Перспективы судов УО по качеству отопления — Как организовать мониторинг температуры в помещениях МКД при ручном регулировании отопления — Горячая вода из крана холодной и наоборот, или подмес воды в квартирах (причины, устранение) — Устранение щелчков в трубах ГВС — Как восст

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

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.

Mentions

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.

Друзья Дональда
@steven_bb · 552,584
Telegram ranks this channel #86 of 86 here — alongside 85 others — read 13 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 6 August 2026 — this entry's latest reading, not the date you are reading this.

“ЧаВо по ЖКХ | ТСЖ, УК, ЖСК и жителям” (@gkhfaq), 431 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/gkhfaq.

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.