Telegram RegisterThe public register of Telegram
Telegram profile photo for 啵啵36d真实-官渡区🈶🏠可外出

Channel

啵啵36d真实-官渡区🈶🏠可外出

@xiongdahuabuduo88

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

529subscribers

+34 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003996084199
TypeChannel
Username@xiongdahuabuduo88
CreatedBetween 1 April 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/xiongdahuabuduo88

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

4955295127 August 2026 — 495 subscribers8 August 2026 — 495 subscribers8 August 2026 — 496 subscribers14 August 2026 — 513 subscribers22 August 2026 — 520 subscribers29 August 2026 — 529 subscribers7 September 2026 — 528 subscribers16 September 2026 — 529 subscribers7 August 202616 September 2026
8 measurements spanning 40 days, net +34. 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 490–534 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 13:59529+1
7 Sept 2026, 17:57528-1
29 Aug 2026, 10:45529+9
22 Aug 2026, 11:48520+7
14 Aug 2026, 13:28513+17
8 Aug 2026, 04:30496+1
8 Aug 2026, 04:20495no change
7 Aug 2026, 18:01495first reading

Engagement

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

What this channel posts

Video runtime
4s
Average length
4s

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

4 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
375.0%
👍125.0%

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

Measured over the 13 most recent posts we hold, published 2 August 2026 to 6 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

6 Aug 2026, 03:14 UTC231 viewsread 8 August 2026
Video

宝贝们,老师回家的路上了,要记得想我噢,爱你们😘,频道不要删掉哈,万一感应到你们想我又再来呢💋

6 Aug 2026, 01:32 UTC240 viewsread 8 August 2026

休息了宝宝们,回家了,期待下次的昆明之约,爱你们😘💋

5 Aug 2026, 05:08 UTC364 views3 reactionsread 8 August 2026
Photo

来都来了,总要吃吃喝喝逛逛再回去吧😜

2👍1

5 Aug 2026, 01:58 UTC363 views1 reactionsread 8 August 2026
Photo

开课了,宝贝,今天最后一天噢,抓紧时间,来最后一发😅

1

4 Aug 2026, 16:02 UTC407 views0 reactionsread 8 August 2026
Photo

❤️云南昆明司机加油站报告❤️ 9分以上为优质,8分以上为中等,7分以下为差超过2次下架黑榜处理! 【时间】:2026-08-04 【老师】: 啵啵 【评价人】:曼哈顿 【人照】:9 【颜值】:9 【身材】:9 【服务】:10 【态度】:9 【环境】:9 【综合评分】:9.17 【过程描述】:抽了个半价劵,知道老师要回老家了,连夜买车票回来出击,一个字很顶,老师很漂亮,很爱干净,该有的服务都有,水中萧,口活差点交代了,赶紧进出正题,一股暖流涌上心头,爽,很会夹,各种各种姿势都来了一遍,结束!

3 Aug 2026, 16:22 UTC471 views0 reactionsread 8 August 2026
Photo

❤️云南昆明司机加油站报告❤️ 9分以上为优质,8分以上为中等,7分以下为差超过2次下架黑榜处理! 【时间】:2026-08-03 【老师】: 啵啵 【评价人】:McJ 【人照】:9 【颜值】:9 【身材】:9.5 【服务】:9.5 【态度】:9 【环境】:9 【综合评分】:9.17 【过程描述】:一早看老师开课就马上预约了,接近中午了没吃饭就过去了。进门后啵啵老师非常热情还问我有没有吃午饭了,可是看到老师的大灯后我只想吃老师😋,接着就是和老师共浴,老师帮我洗得特别认真,还有水中萧真的特别舒服。进入主题AB面按摩,老师的口技非常厉害差点交货了,于是马上带上小雨伞开战,在老师销魂的呻吟声中交货了。结束后和老师一起休息,啵啵老师还分享了她的零食。非常不错的体验还会回锅。

2 Aug 2026, 08:29 UTC595 views0 reactionsread 8 August 2026
Photo

倒计时6天咯,宝宝抓紧时间找我玩吖

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

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

“啵啵36d真实-官渡区🈶🏠可外出” (@xiongdahuabuduo88), 529 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/xiongdahuabuduo88.

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.