Channel
@duoduokebiao7
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,234subscribers
+563 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003804191537 |
|---|---|
| Type | Channel |
| Username | @duoduokebiao7 |
| Created | Between 1 February 2026 and 18 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/duoduokebiao7 |
Giveaways & airdrops — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 |
|---|---|---|
| 16 Sept 2026, 17:17 | 1,234 | +14 |
| 13 Sept 2026, 00:38 | 1,220 | +30 |
| 9 Sept 2026, 10:41 | 1,190 | +3 |
| 3 Sept 2026, 19:16 | 1,187 | +10 |
| 31 Aug 2026, 21:54 | 1,177 | +12 |
| 29 Aug 2026, 01:05 | 1,165 | +29 |
| 25 Aug 2026, 22:33 | 1,136 | +41 |
| 22 Aug 2026, 17:25 | 1,095 | +10 |
| 19 Aug 2026, 08:06 | 1,085 | -42 |
| 16 Aug 2026, 18:03 | 1,127 | +396 |
| 8 Aug 2026, 17:43 | 731 | +60 |
| 8 Aug 2026, 09:00 | 671 | first reading |
20 posts held, back to 18 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
3 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 100.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 3 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 3 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 18 July 2026 to 8 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.
🎉 米其林 徐汇区 多多 抽奖活动 📝 抽奖说明：参加抽奖前，请先考虑交通情况，以免浪费奖额。 https://t.me/moduguangmingding2/19639 https://t.me/godagent007/461 关注ls的频道之后再点击下列按钮可参加抽奖。 中奖后凭抽奖机器人消息、或者频道中公布的名单，直接联系ls兑奖； 如未另行约定，惯例7天有效，遇红休顺延 评价请发给机器人 @gmdast_bot 更多福利请查看光明顶狼友讨论频道：https://t.me/+THHpZTCKkbMzYWE1 ✅ 参与条件： 1. 加入 多多的后宫 2. 加入 魔都光明顶教学课程展览室2 3. 加入 免费抽奖导航 🎁 奖品内容： • 38红包 × 2 • 300优惠券 × 2 ⏰ 开奖时间：2026-08-15 13:03 👇 点击下方按钮参与抽奖
开课啦🫰
🎰 红包抽奖-多多 @SHduoduo 宠粉福利 📮 参与条件： 🪪 必须设置用户名 🎫 加入-上海泡泡屋修车狼友福利群（备用） 🎫 加入-上海泡泡屋修车公开榜（备用） 🎫 加入-多多的后宫 🎫 加入-上海修车泡泡屋公开榜（免费上榜） 🎫 加入-上海修车泡泡屋福利交流群 └ 🎟️ 发言数大于 10 条 🎁 奖品内容： 💰️ 18红包🧧 × 2 ⚠️ 抽奖说明： （1）开奖后请24小时内联系兑奖 ，因炸号、退群、注销账号、超时未兑等原因，不予兑奖。 （2）刷屏、灌水、纯表情、复制粘贴、无意义对话、删除消息、撤回内容等，一律视为无效发言，取消中奖资格！请用心交流！ （3）中奖后三日内出击，经提醒后未按时出击和未提交报告的，将踢出群聊。 （4）中奖者必须去，使用优惠券并提交报告（禁止转赠） 📅 开奖日期：(北京时间) 2026年08月18日 19时00分00秒
开课咯🈶🈳位😉😉
开课啦 🈶空位🉑预约哦😘
假期结束咯 明天开课啦 🈶🈳位🉑预约哦😘
红袖了🌹
【时间】：2026-07-24 【老师】：多多 【留名】：匿名 【人照】：9.5 【颜值】：9.5 【身材】：9.5 【服务】： 【态度】： 【环境】： 【综合】：9.5 【过程】：人很白，人照无差，胸大大软软的，身材不错，服务态度都很好，身上也是软软的，反应也很敏感，很愉快的一次体验
【时间】：2026-07-24 【老师】：多多 【留名】：lucasw 【人照】：8 【颜值】：8 【身材】：8 【服务】：9 【态度】：10 【环境】：9 【综合】：8.67 【过程】：下午约了多多，见面就喜欢，很有礼貌，声音软软糯糯的，洗澡边洗还边口和胸推，小面一下硬了。揉着大胸就要求去床上，老师害羞的样子和声音就让人想欺负，口了一会儿就忍不住要上了，小穴很紧里面热呼呼的。换了三个姿势就舒服地发射了。情绪价值满满，服务得很贴心自然。还会再去。
开课啦 🈶空位 🉑预约哦🥰🥰🥰
开课咯🈶🈳位😉😉
开课啦🈶空位🉑预约哦😉😉
❤1
Showing the 12 most recent of 20 posts we hold for @duoduokebiao7. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“多多的后宫” (@duoduokebiao7), 1,234 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/duoduokebiao7.
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.