🥰😘感谢客户好评反馈💔十年口碑经营🥰专业靠谱👍值得信懒💋找我满十次免费送一次同等价位的🥰 📱📱📱📱😀😀😀😀
❤6👍2

Channel
@wuhanbaidu1
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
10,734subscribers
+2,611 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002864734183 |
|---|---|
| Type | Channel |
| Username | @wuhanbaidu1 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 October 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 17 October 2026 |
| On Telegram | t.me/wuhanbaidu1 |
Adult — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Oct 2026, 20:35 | 10,734 | -193 |
| 16 Oct 2026, 21:00 | 10,927 | -91 |
| 15 Oct 2026, 17:44 | 11,018 | -65 |
| 14 Oct 2026, 17:41 | 11,083 | -115 |
| 13 Oct 2026, 06:15 | 11,198 | -131 |
| 9 Oct 2026, 04:19 | 11,329 | -191 |
| 4 Oct 2026, 17:58 | 11,520 | -138 |
| 26 Sept 2026, 19:15 | 11,658 | -142 |
| 19 Sept 2026, 16:16 | 11,800 | -17 |
| 17 Sept 2026, 07:38 | 11,817 | -56 |
| 15 Sept 2026, 07:56 | 11,873 | +4,761 |
| 11 Sept 2026, 22:41 | 7,112 | -208 |
| 7 Sept 2026, 10:39 | 7,320 | -2,450 |
| 2 Sept 2026, 22:56 | 9,770 | -78 |
| 31 Aug 2026, 00:13 | 9,848 | -119 |
| 27 Aug 2026, 23:28 | 9,967 | -46 |
| 27 Aug 2026, 00:04 | 10,013 | +8 |
| 26 Aug 2026, 02:25 | 10,005 | +2 |
| 25 Aug 2026, 04:46 | 10,003 | -30 |
| 24 Aug 2026, 01:53 | 10,033 | first reading |
43 posts held, back to 3 August 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 38 pages 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 43 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 35 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.
109 reactions across 30 posts, in 5 distinct kinds. The most used accounts for 35.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 39 | 35.8% | |
| ❤ | 37 | 33.9% | |
| 👍 | 15 | 13.8% | |
| 🥰 | 10 | 9.17% | |
| 👏 | 8 | 7.34% |
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 31 of the 43 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 109 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 43 most recent posts we hold, published 3 August 2026 to 28 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.
🥰😘感谢客户好评反馈💔十年口碑经营🥰专业靠谱👍值得信懒💋找我满十次免费送一次同等价位的🥰 📱📱📱📱😀😀😀😀
❤6👍2
🍎🍎🍎🍎🍎🫕:武汉高端外围🌸95半套❤️🔥98全套莞式一条龙🈴平价上门👍🉑全城安排👏口碑经营😘🥰📱📱📱📱📱📱📱📱 私信❤️🔥: @wuhanbaidu0 双向😋: @wuhanbaidubot 电话💌: 18216083193
👍8🔥1
😎兼职大学生💚沐子 07舌吻69,175净身高 艺名:沐子 女大兼职刚下海 贯籍:安徽 年龄:07年19岁 身高:净身高175 体重:55kg 胸围:小C 服务:🐍💋 69 口活 鸳鸯浴 丝袜 情趣制服配度💯 优点:性格开朗活泼,萝御双休,情商高完美女友款,耐操欢迎桩机挑战,纹身情况:后背有线条其它地方没纹身 💦多紧,清纯而绝美的颜值哥哥在冲刺的时候更愿意面对这张漂亮的脸蛋儿,而不是喜欢后入…… 🈲WT 🈲💊 🈲无素质人 所有照片均为真人拍摄 所见君所得 定不负君心
🔥7
🥰极品兼职萝莉🫙淼淼 年纪19 身高160 体重80 🐻C 极品兼职萝莉第一次下海每天只接一单只接素质课。 🉑🐍吻🉑口🉑69🉑🚗 皮肤雪白全身无任何疤痕🈚纹身 上下双粉逼紧水多声音甜美约到就是赚到。
❤7
🍎🍎🍎🍎🍎🫕:武汉高端外围🌸95半套❤️🔥98全套莞式一条龙🈴平价上门👍🉑全城安排👏口碑经营😘🥰📱📱📱📱📱📱📱📱 私信❤️🔥: @wuhanbaidu0 双向😋: @wuhanbaidubot 电话💌: 18216083193
👏1
🍎🍎🍎🍎🍎🫕:武汉高端外围🌸95半套❤️🔥98全套莞式一条龙🈴平价上门👍🉑全城安排👏口碑经营😘🥰📱📱📱📱📱📱📱📱 私信❤️🔥: @wuhanbaidu0 双向😋: @wuhanbaidubot 电话💌: 18216083193
武汉 极品新人刚下海刚破处 甜甜 大学生毕业暑假兼职刚破处❤️人 净足:167 可甜可御 Age年龄:05 🐻:C 🉑情趣 🉑丝袜 🛁 🉑🐍 其他带开发小白 胸挺雪润 见课碧玺温柔体贴 腿长细直 全身丰满 🉑甜 🉑咸S形的身材 代课如男友 花样姿势等待解锁 主动甜妹范可纯可甜可性感性格好温柔体贴皮肤嫩滑超级白敏感体质私处紧致水多情绪价值高女友感爆棚敏感体质私处紧 柔且浪漫的邂逅!
胸型完美,腿长直,无风尘气息,皮肤冷光白,待课温柔主动,开朗爱笑情商高不催不事见必玺
🔥2❤1
🍎🍎🍎🍎🍎🫕:武汉高端外围🌸95半套❤️🔥98全套莞式一条龙🈴平价上门👍🉑全城安排👏口碑经营😘🥰📱📱📱📱📱📱📱📱 私信❤️🔥: @wuhanbaidu0 双向😋: @wuhanbaidubot 电话💌: 18216083193
❤2🔥1
🍎🍎🍎🍎🍎🫕:武汉高端外围🌸95半套❤️🔥98全套莞式一条龙🈴平价上门👍🉑全城安排👏口碑经营😘🥰📱📱📱📱📱📱📱📱 私信❤️🔥: @wuhanbaidu0 双向😋: @wuhanbaidubot 电话💌: 18216083193
👍1🔥1
🍎🍎🍎🍎🍎🫕:武汉高端外围🌸95半套❤️🔥98全套莞式一条龙🈴平价上门👍🉑全城安排👏口碑经营😘🥰📱📱📱📱📱📱📱📱 私信❤️🔥: @wuhanbaidu0 双向😋: @wuhanbaidubot 电话💌: 18216083193
👍1
🥰😘感谢客户好评反馈💔十年口碑经营🥰专业靠谱👍值得信懒💋找我满十次免费送一次同等价位的🥰 📱📱📱📱😀😀😀😀
❤1
Showing the 12 most recent of 43 posts we hold for @wuhanbaidu1. 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.
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.
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.
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 17 October 2026 — this entry's latest reading, not the date you are reading this.
“武汉95/98💯外围🏘” (@wuhanbaidu1), 10,734 subscribers as measured 17 October 2026. Telegram Register, tgregister.com/channel/wuhanbaidu1.
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.