🌕 一轮明月,共祝丰年。 中秋,是团圆的时节,也是向一路相伴的人送上心意的时刻。借此佳节,向各位客户与伙伴道一声:中秋快乐! 平日里,我们因业务相识,在合作中相知。这份缘分,值得珍惜;这份情谊,也值得在生意之外,送上一份真挚的祝福。 愿各位的辛勤耕耘,迎来丰厚回报; 愿事业步步向前,生活处处如意。 忙时有所成,闲时有所乐,团圆时有满堂欢笑。 🥮 月圆人安,家兴业旺。 祝各位及家人度过一个温馨、圆满的中秋佳节!
❤2🥰2
Channel
@duoduoshuju66
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
23,852subscribers
-1,209 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002559197628 |
|---|---|
| Type | Channel |
| Username | @duoduoshuju66 |
| Description | 出各行业精准数据!联系 @ZLL1233456 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 30 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/duoduoshuju66 |
Hacking & security — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 26 Sept 2026, 05:01 | 23,852 | -332 |
| 19 Sept 2026, 07:55 | 24,184 | -208 |
| 16 Sept 2026, 18:15 | 24,392 | -63 |
| 14 Sept 2026, 20:20 | 24,455 | -81 |
| 13 Sept 2026, 04:00 | 24,536 | -162 |
| 11 Sept 2026, 04:42 | 24,698 | -85 |
| 8 Sept 2026, 09:42 | 24,783 | -49 |
| 5 Sept 2026, 01:41 | 24,832 | -19 |
| 3 Sept 2026, 06:18 | 24,851 | -59 |
| 1 Sept 2026, 21:33 | 24,910 | +2 |
| 31 Aug 2026, 19:58 | 24,908 | +5,171 |
| 30 Aug 2026, 16:37 | 19,737 | +12,314 |
| 27 Aug 2026, 18:24 | 7,423 | -3,306 |
| 26 Aug 2026, 17:35 | 10,729 | -2,471 |
| 25 Aug 2026, 14:46 | 13,200 | -2,267 |
| 24 Aug 2026, 12:13 | 15,467 | -2,522 |
| 22 Aug 2026, 22:16 | 17,989 | -4,087 |
| 21 Aug 2026, 11:55 | 22,076 | -2,151 |
| 19 Aug 2026, 12:44 | 24,227 | -1 |
| 18 Aug 2026, 14:25 | 24,228 | first reading |
21 posts held, back to 26 April 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 54 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 24 September 2026 |
|---|---|
| Posts held | 21 (26 April 2026 – 24 September 2026) |
| Views total | 503 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 13:03 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 2 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.
34 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 76.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 26 | 76.5% | |
| 🔥 | 4 | 11.8% | |
| 🥰 | 2 | 5.88% | |
| 🫡 | 2 | 5.88% |
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 19 of the 21 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 34 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 26 April 2026 to 24 September 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.
🌕 一轮明月,共祝丰年。 中秋,是团圆的时节,也是向一路相伴的人送上心意的时刻。借此佳节,向各位客户与伙伴道一声:中秋快乐! 平日里,我们因业务相识,在合作中相知。这份缘分,值得珍惜;这份情谊,也值得在生意之外,送上一份真挚的祝福。 愿各位的辛勤耕耘,迎来丰厚回报; 愿事业步步向前,生活处处如意。 忙时有所成,闲时有所乐,团圆时有满堂欢笑。 🥮 月圆人安,家兴业旺。 祝各位及家人度过一个温馨、圆满的中秋佳节!
❤2🥰2
🔥 小红书关键词数据 🔖 ✔️ 指定关键词精准抓取 ✔️ 获取相关高意向用户数据 ✔️ 200 条起提 ✔️ T+2 出数 ✔️ 支持指定省份 / 直辖市 📊 精准关键词 · 精准数据 💬 有需要联系:@ZLL1233456
❤3
🔥 移动 / 联通 / 电信 DPI【独立线路】 📊 稳定出数|线路稳定|效果稳定 ⚡ 支持长期稳定合作 📩 有需要直接联系:@ZLL1233456
🫡2
💬【企业 IM 聊天软件|成熟系统|支持定制】 想拥有一套属于自己品牌的聊天软件? 我们提供已经开发完成、可直接运营的企业级 IM 聊天系统,无需从零开发,可在现有成熟系统基础上按照业务需求进行定制。 🔹 单聊 / 群聊 / 客服系统 🔹 红包 / 用户资产管理 🔹 企业管理后台 🔹 功能模块定制 🔹 UI 界面定制 🔹 Logo / 名称 / 品牌定制 🔹 API 接口对接 🔹 独立服务器部署 📱 多端支持 iOS(App Store)|Android|华为应用市场|Web 成熟系统 + 按需定制 + 独立部署 从品牌、功能到后台,都可以根据项目需求进行调整。 ⚡ 无需从零开发,更快完成定制,更快上线运营。 📩 有聊天软件需求,可直接私聊了解 @ZLL1233456
🔥2
🔥 六合渗透劫持|色站渗透劫持 流量决定业绩,获客决定利润。 出六合劫持、色站劫持流量,稳定输出,持续放量, 为推广项目带来更多精准用户,有效降低获客成本,提升整体转化率。 ✅ 每日稳定供量 ✅ 精准流量持续输出 ✅ 覆盖广、质量稳定 ✅ 长期合作,稳定接单 📩 需要的联系!@ZLL1233456
❤1
小红书关键词数据 🔖 ✔️ 按指定关键词抓取 ✔️ 精准获取相关意向用户数据 ✔️ 单个任务 200 条起提 ✔️ T+2 出数 💬 有需要的联系!@ZLL1233456
❤2
📕 小红书 UID 转手机号码 ⚡ UID转换手机号 ⏰ 下午 2 点前提交,当晚出数 📦 单任务最低 200 条起 💰 按成功匹配数量计费 有需要的联系:@ZLL1233456
⭐️ SDK数据 ✔️支持带去重库去重 ✔️支持多个APP混合提单 ✔️全行业可提取 任何APP都可抓取 SDK 诚招代理,直客,有量价格可到冰点,真实客户可免测,可后款 📣 联系 - @ZLL1233456
❤2
🔥 六合渗透劫持|色站渗透劫持 流量决定业绩,获客决定利润。 出六合劫持、色站劫持流量,稳定输出,持续放量, 为推广项目带来更多精准用户,有效降低获客成本,提升整体转化率。 ✅ 每日稳定供量 ✅ 精准流量持续输出 ✅ 覆盖广、质量稳定 ✅ 长期合作,稳定接单 📩 需要的联系!@ZLL1233456
🔥1
🔥 抖音直播间数据 ➤ 运营商:移动 ➤ 支持指定省份 / 地级市 ➤ 5个链接即可提交 ➤ 出数周期:T+3 ➤ 数据格式:裸号 📈 出数稳定 📩 需要的联系:@ZLL1233456
🔥 流量决定业绩,获客决定利润。 【六合】渗透劫持量 稳定输出,为推广提供更多精准流量支持,帮助降低获客成本,提升转化效率。 合作稳定,长期可接。 📩 联系:@ZLL1233456
❤2
📊【法人数据】 全国企业法人数据|长期更新 🔥 支持指定省份或城市 🔥 支持筛选企业或个体 ✅ 数据量大 ✅ 覆盖范围广 ✅ 支持定向筛选 ✅ 格式完整 ✅ 长期稳定更新 📩 需要直接联系:@ZLL1233456
❤3
Showing the 12 most recent of 21 posts we hold for @duoduoshuju66. 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 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“【多多数据】SDK,DPI,六合劫持,色站劫持” (@duoduoshuju66), 23,852 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/duoduoshuju66.
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.