блин кому не жалко голосов буду очень признателен если кинете радиостатик реакции должны размножаться
custom 545650382639783394544custom 545392712948807342818custom 545618277329748633112custom 54566223073656562271

Channel
@hutteer
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
703subscribers
+1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002797245213 |
|---|---|
| Type | Channel |
| Username | @hutteer |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 9 August 2026 |
| On Telegram | t.me/hutteer |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 15:16 | 703 | +1 |
| 9 Aug 2026, 01:16 | 702 | first reading |
15 posts held, back to 26 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 15 (26 July 2026 – 8 August 2026) |
| Views total | 7,297 |
| Reactions total | 1,305 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 01:16 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.
1,305 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 24.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5253753491393908547 | 323 | 24.8% | |
| 💘 | 264 | 20.2% | |
| ❤🔥 | 231 | 17.7% | |
| custom 5409201758134109120 | 166 | 12.7% | |
| custom 5357360961705511667 | 104 | 7.97% | |
| custom 5453927129488073428 | 101 | 7.74% | |
| custom 5456503826397833945 | 66 | 5.06% | |
| custom 5456182773297486331 | 48 | 3.68% | |
| custom 5456622307365656227 | 2 | 0.153% |
Custom emoji. 7 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 15 of the 15 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 1,305reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 26 July 2026 to 8 August 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @hutteer. 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 15 most recent posts we hold for this entry, published 26 July 2026 to 8 August 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.
блин кому не жалко голосов буду очень признателен если кинете радиостатик реакции должны размножаться
custom 545650382639783394544custom 545392712948807342818custom 545618277329748633112custom 54566223073656562271
давайте мне навалим разъебем кнопку реакций💜💜и оформим субскрайб💜💜
custom 545392712948807342852custom 545650382639783394519💘11custom 54561827732974863314
Sticker, posted without a caption
💘23custom 54561827732974863318
потому что на десять девчонок по статистике девять ребят😇
💘92custom 545392712948807342831custom 545618277329748633124custom 54565038263978339453custom 54566223073656562271
ждите фем мердермедиа очень👍🏼круто будет👍🏼вкусно 👍🏼 хватит отписуни делать 👍🏼
custom 525375349139390854767❤🔥29custom 535736096170551166711💘1
да стойте зайки стойте не отписывайтесь в жару тяжело рисовать я исправлюсь
❤🔥63custom 525375349139390854715custom 540920175813410912010💘2custom 53573609617055116672
смотрите какие милые🥹🥹🥹собачкиолени🥹🥹🥹🥹🥹
custom 540920175813410912020custom 53573609617055116676custom 52537534913939085474❤🔥1💘1
ㅤㅤㅤㅤㅤㅤ 🦷.🤩🌟🤩.🦷 Я не знаю, что писать, но вот милости глупости такие🌟 .𝆹﹌𝆺𝅥﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌﹌𝆹𝅥﹌𝆹. -͟͟͞ #Radiostatic /#RS #SparksDuo #HazbinHotel
❤🔥40custom 525375349139390854713custom 53573609617055116678custom 54092017581341091203💘1
СУКА СИКСЕЕЕЕВЕН ПЕЗД НА ПОСТЕ
custom 540920175813410912064❤🔥22custom 535736096170551166715💘1custom 52537534913939085471
нахуй вон из моей башни
💘94❤🔥32custom 540920175813410912026custom 53573609617055116678custom 52537534913939085473
СПАСИБО за подарки звезды спасибо большое
custom 525375349139390854745❤🔥9custom 53573609617055116676custom 54092017581341091202
куча рс говна которое надо дорисовать ждите и жрите
custom 525375349139390854754💘10custom 54092017581341091208❤🔥1custom 53573609617055116671
Showing the 12 most recent of 15 posts we hold for @hutteer. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 176,581 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“hutter хутор” (@hutteer), 703 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/hutteer.
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.