Marketing & affiliate — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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 the other topics.
Growth
49 measurements spanning 81 days, net +4,719. 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 16,006–23,387 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 49
Measured (UTC)
Subscribers
Change
4 Nov 2026, 10:48
21,578
-261
2 Nov 2026, 11:58
21,839
-34
1 Nov 2026, 11:35
21,873
-45
31 Oct 2026, 08:17
21,918
-95
30 Oct 2026, 06:49
22,013
-49
29 Oct 2026, 09:30
22,062
-93
28 Oct 2026, 06:25
22,155
-34
27 Oct 2026, 08:07
22,189
-179
26 Oct 2026, 04:36
22,368
+1,598
25 Oct 2026, 05:29
20,770
-1,164
24 Oct 2026, 08:35
21,934
-369
23 Oct 2026, 07:06
22,303
+2
22 Oct 2026, 06:19
22,301
+26
20 Oct 2026, 21:45
22,275
+14
19 Oct 2026, 18:37
22,261
-2
18 Oct 2026, 21:27
22,263
+15
17 Oct 2026, 20:16
22,248
+11
16 Oct 2026, 22:22
22,237
+5
15 Oct 2026, 19:59
22,232
-11
14 Oct 2026, 21:51
22,243
first reading
Engagement
18 posts held, back to 17 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 60 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
41.7%
avg views ÷ 21,578 subscribers
Avg views / post
9,000
1 post measured
Reaction rate
31.5%
reactions ÷ views · ER floor
Posts in window
1
of 18 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
Window
Rolling 30 days · latest post in window 12 October 2026
Posts held
18 (17 May 2026 – 12 October 2026)
Views total
9,000
Reactions total
2,839
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
4 Nov 2026, 15:36 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
Photos
15
Links
11
Lifetime counters from Telegram’s own channel header, read 4 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
11,040 reactions across 14 posts, in 17 distinct kinds. The most used accounts for 19.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
2,107
19.1%
👍
1,506
13.6%
🐳
1,420
12.9%
❤
1,182
10.7%
🎉
983
8.90%
💯
836
7.57%
🤝
800
7.25%
😁
724
6.56%
❤🔥
412
3.73%
🦄
230
2.08%
⚡
227
2.06%
👌
159
1.44%
🍾
147
1.33%
🥰
147
1.33%
🏆
121
1.10%
🤩
20
0.181%
👏
19
0.172%
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 14 of the 18 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 11,040 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 17 May 2026 to 12 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
Telegram’s own ‘edited’ marker: 1 of 1 post held from the last 30 days (100.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Showing the 12 most recent of 18 posts we hold for @HUC001. 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.
Posts edited after publishing
@HUC001 edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
12 October 2026
Most recent edit
3 November 2026
Posts recorded as deleted after publishing
We recorded 2 posts on @HUC001 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
3 November 2026
Most recent seen missing
3 November 2026
Median time before seen missing
44 days
Seen missing in the last 30 days
2
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.
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 4 November 2026 — this
entry's latest reading, not the date you are reading this.
“HUCACC.COM｜出售高质量社交媒体账户” (@HUC001), 21,578 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/HUC001.
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.
