Channel
@hushyxxx
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
328subscribers
-5 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002680921021 |
|---|---|
| Type | Channel |
| Username | @hushyxxx |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/hushyxxx |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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 |
|---|---|---|
| 19 Sept 2026, 05:18 | 328 | -6 |
| 9 Sept 2026, 23:56 | 334 | -1 |
| 1 Sept 2026, 04:08 | 335 | -3 |
| 24 Aug 2026, 05:07 | 338 | +1 |
| 16 Aug 2026, 18:22 | 337 | +4 |
| 8 Aug 2026, 18:30 | 333 | no change |
| 8 Aug 2026, 18:17 | 333 | first reading |
11 posts held, back to 6 May 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 11 posts for this entry, the most recent from 24 July 2026. An engagement rate over an empty window would be a number about nothing.
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.
50 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 44.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5463068232938176769 | 22 | 44.0% | |
| custom 5215239948420003628 | 20 | 40.0% | |
| custom 5463065329540285950 | 5 | 10.0% | |
| custom 5463102274848965798 | 3 | 6.00% |
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 10 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 50 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 6 May 2026 to 24 July 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.
всем еще раз привет, у меня сгорела кухня, я остался без квартиры, в которой я жил и работал, до ремонта я не могу включить там свет тк пожар случился из-за короткого замыкания и нет горячей воды, если есть желание меня поддержать-вот карта, буду рад любой сумме 2200700832988843 заранее всем спасибо🖤
custom 52152399484200036283
Оно живое одаода🦾 KoruSe, hushy - sunset driverˊˎ- > Слушать на ютуб > Спотифай
custom 54630682329381767692
Video, posted without a caption
Video, posted without a caption
custom 54630682329381767692custom 52152399484200036281
Video, posted without a caption
custom 54630682329381767693custom 52152399484200036281custom 54630653295402859501
File, posted without a caption
custom 52152399484200036282custom 54630682329381767691
File, posted without a caption
custom 54630682329381767694
Video, posted without a caption
custom 54630682329381767695custom 54630653295402859502custom 52152399484200036281
File, posted without a caption
custom 52152399484200036284
File, posted without a caption
custom 54630682329381767695custom 52152399484200036284custom 54631022748489657983custom 54630653295402859502
Photo, posted without a caption
custom 52152399484200036284
Showing the 11 most recent of 11 posts we hold for @hushyxxx. 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.
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 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“hushy” (@hushyxxx), 328 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/hushyxxx.
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.