Telegram RegisterThe public register of Telegram
Telegram profile photo for 惠州糖糖

Channel

惠州糖糖

@huizhoutangtang210

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

321subscribers

-12 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1004488718908
TypeChannel
Username@huizhoutangtang210
CreatedBetween 1 June 2026 and 5 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live19 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/huizhoutangtang210

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

320333326.515 August 2026 — 333 subscribers16 August 2026 — 332 subscribers24 August 2026 — 329 subscribers1 September 2026 — 323 subscribers10 September 2026 — 320 subscribers19 September 2026 — 321 subscribers32115 August 202619 September 2026
6 measurements spanning 35 days, net -12. 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 318–335 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 07:17321+1
10 Sept 2026, 04:40320-3
1 Sept 2026, 15:54323-6
24 Aug 2026, 17:35329-3
16 Aug 2026, 08:58332-1
15 Aug 2026, 17:00333first reading

Engagement

20 posts held, back to 5 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 9 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
12s
Average length
12s

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.

Reaction mix

6 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤233.3%
🥰233.3%
👏116.7%
🤮116.7%

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 6 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 5 July 2026 to 9 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

9 Aug 2026, 08:10 UTC196 viewsread 15 August 2026

宝贝们糖糖换地方开了没有在惠州开,明天有闺蜜过来开需要的可以去她那里👉 @chenchen580580

19 Jul 2026, 07:26 UTC616 viewsread 15 August 2026
Photo

🈳🈳🈳有位置🉑🈷️滴滴糖糖宝贝们😘

16 Jul 2026, 08:55 UTC543 viewsread 15 August 2026

宝贝们糖糖有空🉑🈷️哦滴滴我,开几天要红休了🥰

15 Jul 2026, 05:45 UTC538 views1 reactionsread 15 August 2026
Video

宝贝们糖糖开课了有空🉑🈷️哦滴滴我,开几天要红休了🥰

🤮1

14 Jul 2026, 13:59 UTC443 views0 reactionsread 15 August 2026
Forwarded from @lzcxdd6

惠州逍遥阁报告模板-叁 【出击老师】: #糖糖 @odnnfin 【提交学生】:@a_hjj55 【实际支付费用】:600 【服务日期】: 7月6日 【服务地区】:惠城港汇 【环境与卫生】:优 【人照片相符度】:很相符 (很相符 /基本相符 /差异较大) 【身高与体型参考】:163左右 【目测年龄(估计)】: 18 【服务内容简略】:#kiss #六九 #洗吹做 #鸳鸯浴 【态度/沟通】: 态度很好,很温柔 【需要改进的/需要加强的】:无 【是否愿意回访/推荐】:会 (会 /可能 /不会) 【建议与出击体验总结】: 已经是第二次约这个甜妹了,还记得第一次约她的时候,第一眼就觉得看对眼,长到我的标准上,笑起来很萌很甜。是一个萌妹子,于是在7月6日就在约了一次,这次没有约到头课。开门就对着我笑,主动递水,坐下来聊了一下,主动递水,坐下来聊了一会,就一起去洗澡了。嫩妹就是嫩妹,主打粉嫩,三点都很粉。洗…

Showing the 12 most recent of 20 posts we hold for @huizhoutangtang210. 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 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“惠州糖糖” (@huizhoutangtang210), 321 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/huizhoutangtang210.

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.