Channel
@pravilachata_HG
On this record: Topic · Growth · Engagement · Posts · Cite this entry
40subscribers
+7 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001908978199 |
|---|---|
| Type | Channel |
| Username | @pravilachata_HG |
| Created | 3 July 2023 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/pravilachata_HG |
Other / unclassifiable — 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 30 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 |
|---|---|---|
| 12 Oct 2026, 19:21 | 40 | +2 |
| 3 Oct 2026, 05:36 | 38 | +2 |
| 17 Sept 2026, 13:41 | 36 | -1 |
| 9 Sept 2026, 00:36 | 37 | +2 |
| 23 Aug 2026, 08:17 | 35 | +3 |
| 16 Aug 2026, 16:47 | 32 | -1 |
| 11 Aug 2026, 01:01 | 33 | no change |
| 8 Aug 2026, 22:47 | 33 | first reading |
4 posts held, back to 3 July 2023 — 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 14 May 2026. An engagement rate over an empty window would be a number about nothing.
📣 ПРАВИЛА ГОЛОСОВОГО ЧАТА 📌 (Голосовой чат) ⚖️ Общая система наказаний: • 1 нарушение — предупреждение • 2 нарушение — мут предупреждение не делают если грубое наказание ⚠️1. Провокации Запрещены в любом виде → мут ❌1.1 Троллинг Запрещён троллинг в любом виде → мут/ бан. [обращаем внимание на приписки от кланов] 🤬 2. Оскорбления • Участников → мут • Администрации → мут/бан 🔈 3. Крики / перебивание Если участник крич…
Channel name was changed to «Правила чата»
Правила чата 🖥Категорически запрещено: 👎1. Выдавать себя за представителя Администрации проекта. 🚫 2. Завуалированный мат и слова оскорбительного характера. 🌐 3. Дискриминация по расовому, национальному, религиозному или иному признаку. Националистические, расовые лозунги и высказывания. Сообщения, призывающие к каким-либо действиям против других национальностей. 💬 4. Сообщения/Фото/Стикеры Сексуального и порнографи…
Channel created
Showing the 4 most recent of 4 posts we hold for @pravilachata_HG. 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Правила чата” (@pravilachata_HG), 40 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/pravilachata_HG.
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.