Channel
@huihuam
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
18subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002773110107 |
|---|---|
| Type | Channel |
| Username | @huihuam |
| Created | Between 1 June 2025 and 4 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/huihuam |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 17:46 | 18 | no change |
| 7 Aug 2026, 06:16 | 18 | first reading |
4 posts held, back to 4 August 2025 — 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 pageof 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 4 posts for this entry, the most recent from 8 January 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 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.
Measured directly from 2 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.
😊欢迎加入熊二工作室 😘期待新老顾客一直选择 😉熊二人设套图素材业务如下： 🤩{新}亚洲女性套图 🤩{新}亚洲男性套图 🤩{新}欧洲女性套图 🤩{新}欧洲男性套图 🤩{新}私密女性套图 😝疯狗精聊业务全方位掌控： 😛【美工】证件P图 😛【绘画】私人定制 😛【代洗】人物照片 😛【代开】飞机会员 😛【商务】广告推广 😛【代写】人设定位 😛【熊二】频道拉人 😝【熊二】ai建模换脸 😝【熊二】电话轰炸 😝【熊二】礼物代购 😝【熊二】 海外话术 😝【熊二】 海外素材 😝【熊二】吃瓜中心 😝【熊二】新闻资讯 😝【熊二】东南亚大事 😛客服：@xiongerid 支付方式：😞😆🤯😫😆😢😗🙂↕️😘😤😭
【熊二】工作室 绘画，主要目的是增加感情，因为是网聊，没有什么是比送一副绘画更容易拉近之间的关系，聊出爱情的感觉。 这个客户能入金就送画，铺垫给客户准备了一份礼物，灵活的分开几天运用画的素材，每天都能用画的素材去展开话题。 ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ 仅此客服：@xiongerid
【熊二】工作室 绘画，主要目的是增加感情，因为是网聊，没有什么是比送一副绘画更容易拉近之间的关系，聊出爱情的感觉。 这个客户能入金就送画，铺垫给客户准备了一份礼物，灵活的分开几天运用画的素材，每天都能用画的素材去展开话题。 ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ 仅此客服：@xiongerid
【熊二】工作室 绘画，主要目的是增加感情，因为是网聊，没有什么是比送一副绘画更容易拉近之间的关系，聊出爱情的感觉。 这个客户能入金就送画，铺垫给客户准备了一份礼物，灵活的分开几天运用画的素材，每天都能用画的素材去展开话题。 ➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖ 仅此客服：@xiongerid
Showing the 4 most recent of 4 posts we hold for @huihuam. 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.
Citation-graph rank — 1,033,214 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
@huihuam named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“绘画 素描 彩绘 水彩 私人定制 人设包装” (@huihuam), 18 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/huihuam.
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.