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 100% 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.
Growth
33 measurements spanning 43 days, net +1,026. 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 27,707–29,041 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)
Subscribers
Change
19 Sept 2026, 12:58
28,887
+62
17 Sept 2026, 03:40
28,825
+299
15 Sept 2026, 01:21
28,526
-1
13 Sept 2026, 11:19
28,527
+27
11 Sept 2026, 16:00
28,500
+75
9 Sept 2026, 01:57
28,425
+39
5 Sept 2026, 16:57
28,386
+47
3 Sept 2026, 14:42
28,339
+19
2 Sept 2026, 05:04
28,320
+10
1 Sept 2026, 03:18
28,310
+33
31 Aug 2026, 02:13
28,277
+38
30 Aug 2026, 02:58
28,239
+22
29 Aug 2026, 05:24
28,217
+16
28 Aug 2026, 03:34
28,201
+6
27 Aug 2026, 04:11
28,195
+18
26 Aug 2026, 06:16
28,177
+36
25 Aug 2026, 03:43
28,141
-2
23 Aug 2026, 21:54
28,143
-7
22 Aug 2026, 08:18
28,150
+26
20 Aug 2026, 19:36
28,124
first reading
Engagement
209 posts held, back to 1 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 64 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
27.4%
avg views ÷ 28,887 subscribers
Avg views / post
7,930
103 posts measured
Reaction rate
1.07%
reactions ÷ views · ER floor
Posts in window
103
of 209 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
Window
Rolling 30 days · latest post in window 23 September 2026
Posts held
209 (1 August 2026 – 23 September 2026)
Views total
816,320
Reactions total
8,735
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
23 Sept 2026, 11:37 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
≈6,570
Videos
≈1,780
Links
≈1,250
Lifetime counters from Telegram’s own channel header, read 23 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
19m 46s
Average length
34s
Measured directly from 35 videos 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.
Reaction mix
16,642 reactions across 209 posts, in 17 distinct kinds. The most used accounts for 35.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
5,948
35.7%
😢
3,361
20.2%
🤬
2,764
16.6%
🤯
1,319
7.93%
😁
902
5.42%
😱
385
2.31%
🫡
374
2.25%
🔥
320
1.92%
👏
300
1.80%
🙏
216
1.30%
🤔
185
1.11%
😍
164
0.985%
💅
156
0.937%
🤷♂
84
0.505%
🐳
80
0.481%
🗿
66
0.397%
🎉
18
0.108%
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 209 of the 209 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 16,642 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 209 most recent posts we hold, published 1 August 2026 to 23 September 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.
Telegram Stars
Stars received
29
across the posts below
Posts paid on
19
of 209 we hold a reading for · 9%
Most on one post
5
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @hyevuy_alex. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 209 most recent posts we hold for this entry, published 1 August 2026 to 23 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Внаслідок чергової ворожої атаки на околицях Кропивницького зазнало пошкоджень одне з місцевих підприємств.
У складській будівлі вибуховою хвилею вибито вікна. Обстеження території триває.
Найголовніше – минулося без загиблих та травмованих.
Зберігайте спокій та не ігноруйте сигнали повітряної тривоги!
• голова ОВА Райкович
У неділю, 27 вересня, в рамках 9-го туру 😀Першої ліги України, домашній матч проти ФСК «Фенікс-Маріуполь»!🖤💛💚
🆚 😀«Олександрія» - 😀«Фенікс-Маріуполь»
⏰ 27 вересня, 14:00
🏟 КСК «Ніка», м. Олександрія
42% ДТП з постраждалими цьогоріч сталися через порушення швидкості. На такі автопригоди припадає також 55% від усіх загиблих на дорогах.
Кількість аварій, що сталися через порушення швидкісного режиму, зростала протягом останніх 10 років, за винятком 2021-2022 рр. Втім торік кількість таких аварій сягнула максимуму за останні 10 років — 10 599 ДТП з постраждалими.
Загалом такі ДТП забрали життя понад 16 тисяч людей…
#промо
Привіт!
Ми — «Алкогрупа», і наш склад шукає супергероїв фізичної праці! 🥰
Якщо ти активний, не любиш сидіти на місці та хочеш стабільно заробляти — ти знайшов правильне місце.💪🏼
Запрошуємо у свою команду вантажника!
✅ Графік роботи: Пн-Пт з 08:00-18:00
✅ Заробітна платня: 22 000 грн
✅ Безкоштовні гарячі обіди
Для подачі заявки телефонуйте: 0638807747 Аліна
💦 Інформація про стан водопостачання на об’єктах ОКВП «Дніпро-Кіровоград» станом на 23 вересня.
☝️Олександрія
📍аварійно-ремонтні роботи по провулку Кармелюка.
В громадах Олександрійського району, що постраждали від ворожої атаки, почали працювати спеціальні комісії.
Вони обстежують вражені домоволодіння і фіксують ступінь пошкоджень.
- голова ОВА Райкович
Отримали інформацію про ще один пошкоджений будинок внаслідок ворожої атаки. Зафіксовано незначні руйнування приватного домоволодіння в Великоандрусівській громаді Олександрійського району.
Найголовніше – повідомлень про загиблих чи травмованих не надходило. Фахівці обстежать усі руйнування задля необхідної допомоги господарям оселі.
Тим часом в Попельнастівській громаді нараховано вже 7 пошкоджених будинків.
• г…
‼️Олександрійщина!
22, 23 та 24 вересня з 15.00 до 22.00 в Олександрійському районі проводитимуться тактичні навчання.
Не лякайтесь гучних звуків і зберігайте спокій.
💦Інформація про стан водопостачання на об’єктах ОКВП «Дніпро-Кіровоград» станом на 9.00 ранку 22 вересня.
☝️Олександрія
📍аварійно-ремонтні роботи по проспекту Соборний.
Внаслідок ворожої атаки в Попельнастівській громаді Олександрійського району зруйновано приватний будинок. Ще декілька домоволодінь – пошкоджені.
Наразі інформації про загиблих та постраждалих не надходило.
Ситуацію відслідковуємо.
• голова ОВА Райкович
😢49🤬10❤4
Showing the 12 most recent of 209 posts we hold for @hyevuy_alex. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
The shares total 106%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 209 most recent posts we hold, published 1 August 2026 to 23 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
Олександрія @olexsanriya · 21,944 Telegram ranks this channel #1 of 68 here — alongside 67 others — read 22 September 2026
Сергій Кузьменко / Олександрія @s_kuzmenko_official · 23,222 Telegram ranks this channel #1 of 66 here — alongside 65 others — read 18 September 2026
Кіровоградська Правда @k_pravda · 46,740 Telegram ranks this channel #4 of 67 here — alongside 66 others — read 27 August 2026
🇺🇦 Андрій Райкович/ Кіровоградська ОДА (ОВА) @kirovogradskaODA · 64,945 Telegram ranks this channel #14 of 82 here — alongside 81 others — read 21 August 2026
❗️СИРЕНА КІРОВОГРАДЩИНА🔊 @surenakrop · 52,671 Telegram ranks this channel #15 of 60 here — alongside 59 others — read 24 August 2026
Труха⚡️Кропивницький @truexakropivnicky · 186,460 Telegram ranks this channel #20 of 76 here — alongside 75 others — read 12 August 2026
Кропивницький ⚡️Новини @kropyvnytskyi_insider · 22,606 Telegram ranks this channel #22 of 86 here — alongside 85 others — read 20 September 2026
ХК | Кропивницький 🇺🇦 @xk_krop · 38,299 Telegram ranks this channel #32 of 64 here — alongside 63 others — read 1 September 2026
kirovograd_official🇺🇦Кропивницький @kirovograd_official · 75,242 Telegram ranks this channel #41 of 68 here — alongside 67 others — read 19 August 2026
This channel appears in 9 seed channels' Telegram-generated recommendation lists 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 19 September 2026 — this
entry's latest reading, not the date you are reading this.
“ХУАлекс | Олександрія” (@hyevuy_alex), 28,887 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/hyevuy_alex.
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.