На этом интерактив закончен. Спасибо всем кто участвовал и проявлял активность, а с вами был ваш Чейз, до новых встреч.
custom 52267210574272016402custom 53212979252072546231
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ

Channel
@HUG4STEN_A
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
469subscribers
+47 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003832568544 |
|---|---|
| Type | Channel |
| Username | @HUG4STEN_A |
| Created | Between 1 February 2026 and 28 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/HUG4STEN_A |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 |
|---|---|---|
| 16 Sept 2026, 14:18 | 469 | -13 |
| 9 Sept 2026, 08:15 | 482 | -7 |
| 31 Aug 2026, 22:38 | 489 | -9 |
| 25 Aug 2026, 00:26 | 498 | +64 |
| 16 Aug 2026, 15:25 | 434 | +12 |
| 8 Aug 2026, 05:30 | 422 | no change |
| 7 Aug 2026, 19:03 | 422 | first reading |
13 posts held, back to 28 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 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 13 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
32 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5226721057427201640 | 16 | 50.0% | |
| custom 5321297925207254623 | 9 | 28.1% | |
| custom 5323711069762381423 | 7 | 21.9% |
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 7 of the 13 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 32 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 28 July 2026 to 1 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.
На этом интерактив закончен. Спасибо всем кто участвовал и проявлял активность, а с вами был ваш Чейз, до новых встреч.
custom 52267210574272016402custom 53212979252072546231
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
шестая пара. @– 💍 @–
custom 52267210574272016403custom 53237110697623814232custom 53212979252072546231
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
пятая пара. @MORI7S 💍 @–
custom 53212979252072546231custom 53237110697623814231
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
активнее.
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
четвертая пара. @ffu7el 💍 @arielsw
custom 52267210574272016403custom 53212979252072546232custom 53237110697623814231
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
третья пара. @– 💍 @H3RZBLTT
custom 52267210574272016402
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
вторая пара. @– 💍 @Kiara_Fal
custom 52267210574272016402custom 53212979252072546232
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
давайте больше рк!
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
8рк и 3 комм - продолжаю.
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
первая пара. @klliwwq 💍 @BL0ND44
custom 52267210574272016404custom 53237110697623814233custom 53212979252072546232
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
начинаю.
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
ИНТЕРАКТИВ ШИППЫ ОТ ЧЕЙЗА чтобы попасть на инт вам надо соблюдать такие пункты: – подписаны на канал. – авы только не берут рофл/рж/аниме или закрытая. – так же, если у вас стоит совма, то указывайте какую аватарку брать. – актив и рп. НАБОР ДО 12 ЧЕЛОВЕК. под набором ставим точку и ссылку чата на рассылку, лишнего не пишем
Signed 𝐀𝐍𝐓𝐀𝐆𝐎𝐍𝐈𝐒.ᵐᵒʳᵍᵃⁿ
Showing the 12 most recent of 13 posts we hold for @HUG4STEN_A. 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.
Named by 3 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Hūgèstèn.” (@HUG4STEN_A), 469 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/HUG4STEN_A.
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.