Telegram RegisterThe public register of Telegram
Telegram profile photo for h u g a b e a t z

Channel

h u g a b e a t z

@hugabeatz

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

174subscribers

+29 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001806714138
TypeChannel
Username@hugabeatz
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 October 2026
Last confirmed live9 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/hugabeatz

Topic

Music — 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 9 October 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

145174159.59 August 2026 — 145 subscribers9 August 2026 — 146 subscribers15 August 2026 — 147 subscribers30 August 2026 — 156 subscribers29 September 2026 — 171 subscribers9 October 2026 — 171 subscribers9 October 2026 — 174 subscribers9 August 20269 October 2026
7 measurements spanning 61 days, net +29. 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 141–178 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Oct 2026, 09:02174+3
9 Oct 2026, 08:23171no change
29 Sept 2026, 06:58171+15
30 Aug 2026, 12:14156+9
15 Aug 2026, 19:35147+1
9 Aug 2026, 08:41146+1
9 Aug 2026, 00:45145first reading

Engagement

11 posts held, back to 25 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
111.5%
avg views ÷ 174 subscribers
Avg views / post
194
5 posts measured
Reaction rate
7.53%
reactions ÷ views · ER floor
Posts in window
5
of 11 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 1 October 2026
Posts held11 (25 August 2026 – 1 October 2026)
Views total970
Reactions total73
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Oct 2026, 08:23 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

Video runtime
1m 22s
Average length
21s

Measured directly from 4 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

205 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 37.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52129201335042124567637.1%
custom 57760364653686330433115.1%
custom 52132851327099294742914.1%
custom 54157222185690897672914.1%
custom 52246072677976068372411.7%
custom 5247076664084543509167.80%

Custom emoji. Every row above is a 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 are Telegram’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 11 of the 11 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 205 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 25 August 2026 to 1 October 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.

Recent posts

1 Oct 2026, 23:21 UTC111 views16 reactionsread 9 October 2026
Photo

Новый релиз⚡️ PODLESNOV, HUGEKILLA - DONT STOP 🌟 Слушать на площадках🎧

custom 52129201335042124568custom 52132851327099294743custom 57760364653686330433custom 52246072677976068371custom 52470766640845435091

19 Sept 2026, 13:34 UTC163 views7 reactionsread 9 October 2026

Сохраняйте ❤️ https://braat.band.link/5kW0o https://braat.band.link/5kW0o https://braat.band.link/5kW0o

custom 52129201335042124564custom 57760364653686330433

19 Sept 2026, 11:16 UTC169 views16 reactionsread 9 October 2026
Video

Новый трек 02/10🧯🧯🧯 PODLESNOV, HUGEKILLA - DONT STOP

custom 52129201335042124568custom 57760364653686330435custom 52246072677976068373

18 Sept 2026, 14:04 UTC144 views21 reactionsread 9 October 2026

Ну че, когда сливать Малинки?🔥

custom 521292013350421245615custom 57760364653686330434custom 54157222185690897672

18 Sept 2026, 14:04 UTC383 views13 reactionsread 9 October 2026
Video message

Video message, posted without a caption

custom 52129201335042124567custom 57760364653686330433custom 52132851327099294742custom 54157222185690897671

10 Sept 2026, 09:11 UTC204 views23 reactionsread 9 October 2026
Video

Мы тут с Саней на наш трек рилс сделали 🤝💨

custom 52132851327099294749custom 52129201335042124566custom 52246072677976068375custom 54157222185690897673

9 Sept 2026, 18:15 UTC160 views25 reactionsread 9 October 2026
Video

💨

custom 521292013350421245612custom 52246072677976068376custom 54157222185690897676custom 52132851327099294741

29 Aug 2026, 09:34 UTC227 views33 reactionsread 9 October 2026
Photo

🤝

custom 541572221856908976714custom 521292013350421245610custom 57760364653686330437custom 52246072677976068372

25 Aug 2026, 06:04 UTC226 views21 reactionsread 9 October 2026

А это всё на моем сете было. Демоны 😭😭😭

custom 52129201335042124566custom 52470766640845435096custom 52132851327099294745custom 52246072677976068374

25 Aug 2026, 06:04 UTC206 views23 reactionsread 9 October 2026
Video

Video, posted without a caption

custom 52132851327099294747custom 52470766640845435097custom 57760364653686330436custom 52246072677976068373

25 Aug 2026, 06:02 UTC173 views7 reactionsread 9 October 2026

Смотрите какая жига была 🤌🏽🤌🏽🤌🏽

custom 54157222185690897673custom 52132851327099294742custom 52470766640845435092

Showing the 11 most recent of 11 posts we hold for @hugabeatz. 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

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

Named by 1 registered channel — 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.

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

“h u g a b e a t z” (@hugabeatz), 174 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/hugabeatz.

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.