Telegram RegisterThe public register of Telegram
Telegram profile photo for 荟荟的秘密基地

Channel

荟荟的秘密基地

@huihuidehouhua

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

683subscribers

+141 since we began measuring on 25 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003487711408
TypeChannel
Username@huihuidehouhua
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live19 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/huihuidehouhua

Topic

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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.

Growth

542683612.525 August 2026 — 542 subscribers26 August 2026 — 544 subscribers3 September 2026 — 659 subscribers11 September 2026 — 645 subscribers19 September 2026 — 683 subscribers25 August 202619 September 2026
5 measurements spanning 25 days, net +141. 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 521–704 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 07:42683+38
11 Sept 2026, 05:36645-14
3 Sept 2026, 02:37659+115
26 Aug 2026, 11:02544+2
25 Aug 2026, 13:45542first reading

Engagement

20 posts held, back to 19 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 20 posts for this entry, the most recent from 22 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 06s
Average length
17s

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.

Reaction mix

8 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 87.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤787.5%
🍌112.5%

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 6 of the 20 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 19 July 2026 to 22 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.

Recent posts

22 Aug 2026, 03:50 UTC316 views4 reactionsread 25 August 2026
Photo

25号回三亚啦 有没有想我的宝宝 可提前预约哦 爱你们 🥰

❤4

7 Aug 2026, 17:09 UTCviews —

荟荟的后宫 pinned «回老家啦宝宝们❤️勿扰哦!回三亚的话会提前发频道的 🥰»

7 Aug 2026, 17:08 UTC807 viewsread 25 August 2026

回老家啦宝宝们❤️勿扰哦!回三亚的话会提前发频道的 🥰

1 Aug 2026, 07:52 UTC≈1,130 views1 reactionsread 25 August 2026
Video

小可爱上线了,宝宝们可以预约了😜😜😜😜😜

🍌1

30 Jul 2026, 14:03 UTC≈1,010 views1 reactionsread 25 August 2026
Forwarded from @hainanbaogao

海南茶院专属报告模板 @hainanchayuan 🏷基础信息 【老师艺名】:荟荟 【榜单来源】:茶艺榜 @hainanchayi 【验证留名】:松松得得 【验证时间】:2026-07-30 【品茶费用】:9p 【位置地区】:三亚 💯综合评价 【总体评价】:10.0 【颜值评分】:10.0 【服务评分】:10.0 评分标准:5及以下差, 6分为良,7分为精,8分为优,9分为佳,10分为绝 👙软硬配置 【熊器尺寸】:大小合适,特别舒适 【紧度湿度】:完美,不容错过 【优点缺点】:情绪价值拉满 💋自由发挥 【过程描述】:粥香袅袅暖心头, 粥甜入口解千愁。 好景良辰常相伴, 美好时光慢慢流。 遥控上楼,进门看到妹妹的瞬间,高颜值曲线完美,随即交水费洗澡,看妹妹完美的肉体一步步呈现在面前,洗澡之前先漱口,妹妹陪浴认真,有一说一,是cj以来第一次能让我洗澡时候就起立的,妹妹的笑超甜…

❤1

29 Jul 2026, 14:29 UTC848 viewsread 25 August 2026
Video

在三亚最后一个星期就回老家休息啦 约课的宝宝提前发信息确定时间 爱你们 ❤️

Showing the 12 most recent of 20 posts we hold for @huihuidehouhua. 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.

Forward network

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.

Mentions

Named by 2 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.

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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“荟荟的秘密基地” (@huihuidehouhua), 683 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/huihuidehouhua.

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.