Молодец
Signed WINSFEG

Channel
@huliiiinet
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
152subscribers
-40 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003575446361 |
|---|---|
| Type | Channel |
| Username | @huliiiinet |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/huliiiinet |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 2 Oct 2026, 00:57 | 152 | -10 |
| 17 Sept 2026, 10:18 | 162 | -4 |
| 9 Sept 2026, 06:00 | 166 | -13 |
| 31 Aug 2026, 07:25 | 179 | -3 |
| 24 Aug 2026, 10:08 | 182 | -8 |
| 15 Aug 2026, 19:32 | 190 | -2 |
| 8 Aug 2026, 11:50 | 192 | no change |
| 7 Aug 2026, 18:26 | 192 | first reading |
16 posts held, back to 5 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
19 reactions across 4 posts, in 9 distinct kinds. The most used accounts for 26.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5170337581463766147 | 5 | 26.3% | |
| custom 5202180086744244002 | 3 | 15.8% | |
| custom 5170299369139733798 | 2 | 10.5% | |
| custom 5183836332962612325 | 2 | 10.5% | |
| custom 5184191509578122460 | 2 | 10.5% | |
| custom 5398029581829571532 | 2 | 10.5% | |
| custom 5334812499365621269 | 1 | 5.26% | |
| custom 5424640597900162763 | 1 | 5.26% | |
| custom 5424793863808119159 | 1 | 5.26% |
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 4 of the 16 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 19 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 5 August 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.
Молодец
Signed WINSFEG
любята, я отпраздновал с кайфом, можно жить🌟
Signed Mr.Klöđ
сяб брат
Signed Mr.Klöđ ☥
С днюхой бро
Signed WINSFEG
Sticker, posted without a caption
Signed Mr.Klöđ ☥
с днем рождения меня🎉
Signed Mr.Klöđ ☥
На этом все.
Signed WINSFEG
File, posted without a caption
Signed WINSFEG
4 ПАРА
custom 51838363329626123252
Signed WINSFEG
File, posted without a caption
Signed WINSFEG
3 ПАРА
custom 51703375814637661472custom 51702993691397337981custom 51841915095781224601custom 52021800867442440021custom 53348124993656212691custom 54246405979001627631custom 54247938638081191591
Signed WINSFEG
File, posted without a caption
Signed WINSFEG
Showing the 12 most recent of 16 posts we hold for @huliiiinet. 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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“Frězens” (@huliiiinet), 152 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/huliiiinet.
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.