Telegram RegisterThe public register of Telegram
Telegram profile photo for «ХАСэнерго»

Channel

«ХАСэнерго»

@HASENERGO

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

16,012subscribers

+100 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001488390088
TypeChannel
Username@HASENERGO
DescriptionХасавюртовское городское отделение По вопросам электроснабжения можно круглосуточно обращаться на «горячую линию» компании «Россети» по телефону 8-800-220-0-220 (звонок бесплатный).
Created22 January 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/HASENERGO

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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 the other topics.

Growth

15,90616,05615,98116,0126 August 202611 November 2026
63 measurements spanning 98 days, net +100. 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 15,884–16,079 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
11 Nov 2026, 20:2716,012+12
9 Nov 2026, 22:5516,000+16
8 Nov 2026, 17:1715,984-11
7 Nov 2026, 08:5815,995+2
6 Nov 2026, 12:2615,993+1
5 Nov 2026, 14:5915,992+9
4 Nov 2026, 12:2515,983-7
3 Nov 2026, 08:5615,990+3
2 Nov 2026, 07:5915,987-12
1 Nov 2026, 08:0415,999-8
31 Oct 2026, 06:4016,007-1
30 Oct 2026, 08:1616,008+1
29 Oct 2026, 11:2816,007-4
27 Oct 2026, 13:1616,011-9
26 Oct 2026, 10:3616,020-6
25 Oct 2026, 10:0816,026-2
24 Oct 2026, 12:2716,028-4
23 Oct 2026, 15:3616,032+16
22 Oct 2026, 15:4416,016-7
21 Oct 2026, 13:3116,023first reading

Engagement

59 posts held, back to 21 July 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 77 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
37.9%
avg views ÷ 16,012 subscribers
Avg views / post
6,070
15 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
15
of 59 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held59 (21 July 2026 – 11 November 2026)
Views total91,090
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 06:52 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
417
Videos
567
Links
57

Lifetime counters from Telegram’s own channel header, read 14 November 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.

Video runtime
24s
Average length
24s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

Telegram’s own ‘edited’ marker: 5 of 15 posts held from the last 30 days (33.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 06:34 UTC≈2,630 viewsread 14 November 2026
Photo

Внеплановое отключение пс Акташ фидер 8 с 09:40 по 12:00. Обрезка деревьев.

10 Nov 2026, 08:34 UTC≈3,270 viewsread 14 November 2026

Внимание плановые работы! 11.11.2026 С 09-00 до 12-00 Ф4 и Ф8 Акташ будут отключены в связи с работами по обрезке ветвей деревьев и заменой изоляторов

6 Nov 2026, 14:16 UTC≈4,880 viewsread 14 November 2026

Ф8 Ярыксу аварийное отключение. Дежурная смена выехала на поиски причин отключения

5 Nov 2026, 11:05 UTC≈5,720 viewsread 14 November 2026

Ф11 Ярыксу начало линии Пос. Садовый включили (25%). Дальше обход по линии продолжается.

5 Nov 2026, 07:56 UTC≈5,790 viewsread 14 November 2026

Ф 11 Ярыксу аварийное отключение Бригада на обходе по линии. Время включения пока неизвестно

1 Nov 2026, 16:23 UTC≈7,360 viewsread 14 November 2026

Внимание отключение 02.11.2026 С 5:30 по 07:00 Плановое отключение фидеров4и 8 пс Акташ. Обрезка деревьев.

31 Oct 2026, 08:12 UTC≈6,660 viewsread 14 November 2026

Ф6 Акташ неотложное отключение. Ремонтные работы до 12-00

31 Oct 2026, 06:32 UTC≈6,280 viewsread 14 November 2026

Ф4 Акташ неотложное отключение. Ремонтные работы до 11-30

29 Oct 2026, 13:38 UTC≈7,220 viewsread 14 November 2026

Внимание отключение 30.10.2026 С 5:30 по 07:00 Плановое отключение фидера 8 пс Акташ. Обрезка деревьев.

26 Oct 2026, 11:28 UTC≈7,300 viewsread 14 November 2026

Ф6 акташ в связи с работами на линии ожидается отключение с 16-00 до 19-00

26 Oct 2026, 10:51 UTC≈7,170 viewsread 14 November 2026

Внимание отключение 27.10.2026г С 10:00 по 13:00 Плановые работы в трансформаторном пункте 93 Пс Акташ ф6. (Частично) Без электроснабжения П. АЭРОДРОМ ДАЧИ Пром. зона. Трасса Аксай-Хасавюрт.

22 Oct 2026, 18:03 UTC≈6,930 viewsread 14 November 2026

Ф7 ярыксу аварийное отключение. Место повреждения обнаружено. Принимаются меры по устранению повреждения. Приблизительное время включения линии 22-30

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

Posts edited after publishing

@HASENERGO edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
14 August 2026
Most recent edit
14 August 2026

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“«ХАСэнерго»” (@HASENERGO), 16,012 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/HASENERGO.

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.