Channel
@duidui007
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,049subscribers
+32 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001886214009 |
|---|---|
| Type | Channel |
| Username | @duidui007 |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/duidui007 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 23:47 | 2,049 | +24 |
| 10 Aug 2026, 23:21 | 2,025 | +8 |
| 7 Aug 2026, 15:02 | 2,017 | no change |
| 7 Aug 2026, 12:59 | 2,017 | first reading |
20 posts held, back to 5 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 1 pageof 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. It is computed over the 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (5 August 2026 – 7 August 2026) |
| Views total | 4,699 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 15:02 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 1 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 1reactions 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 August 2026 to 7 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.
😉😉😹😻😼😼😉😉 💕体育产品总监 💕深圳南山 💕💕岗位职责 全权负责海外体育竞技类产品整体规划，聚焦竞技对战、赛事竞玩、比分推演、体育闯关、球星对战等核心竞技玩法设计，面向东南亚、拉美等海外市场制定产品周期规划，对流水、付费转化、次日 / 7 日留存、LTV 核心指标负责。 深挖海外球迷喜好（足球、篮球、美式体育为主），结合联赛赛程周期性上新竞技模式：实时赛事对战、多人 PK 竞技、赛季天梯排位、赛事挑战赛、球星阵容养成竞技体系，完成玩法创新、迭代、淘汰全生命周期管理。 搭建竞技商业化体系：竞技门票、赛季通行证、球星卡牌养成礼包、竞技专属道具、段位特权会员等变现模块设计，兼顾竞技平衡性与营收收益，避免逼氪流失。 以数据驱动竞技玩法迭代，分析对战胜率、玩法参与率、付费节点、流失节点，落地 A/B 测试优化竞技平衡性、匹配机制、奖励体系，提升用户竞技时长与复玩频次。 联动研发、风控、运营、本地化团队落地版本排期、灰度上线、…
❤1
😉😉😹😻😼😼😉😉 #第三国远程 #产品总监 ❤️包网产品总监 ❤️项目：巴西市场及其他海外包网 项目经验必须 🌹🌹岗位职责 1 . 负责公司游戏平台（包网、电子、真人、体育、棋牌等）的整体产品规划、路线图及版本管理，对产品结果负责。 2. 管理产品需求及优先级，负责需求评审，确保产品逻辑、用户体验及开发效率。 3. 管理产品、UI、UX团队，建立产品流程、PRD及需求评审规范。 4. 协调开发、测试、UI等团队，推动项目按计划上线并保障交付质量。 5. 持续分析市场、竞品及用户需求，优化活动、VIP、推广、游戏大厅、留存及充值转化体系。 6. 建立数据驱动的产品优化机制，关注DAU、留存率、充值率、ARPU/ARPPU、活动ROI及用户转化等核心指标。 7.持续优化用户体验、操作流程及产品商业化能力。 任职要求 1. 5年以上互联网产品经验，3年以上产品团队管理经验。 2. 有完整产品负责人经验，能够独立负责产品规…
😉😉😹😻😼😼😉😉 🍾马来吉隆坡 #专员薪资：3500U #经理薪资：5000U #投递要求：不限制国籍。人目前在马来持有合法签证即可 #时间：10:00-19:00，单休(周六居家办公） #待遇：餐房补5000马币，只外宿 #项目：体育包网 中国市场 社交软件app 😉😉联系：@Mario1133 😉😉频道：@duidui007
😉😉😹😻😼😼😉😉 #运维 #越南 #居家 #远程 ♈️越南办公♈️远程居家♈️不压护照♈️ 🇵🇳（远程办公//不压护照//要求人在越南）🥰🟢 🙂🙂 急招一名： 运维工程师 🥰 温馨提示：+ 要求人选在越南，不接收其它地方办公 + 学历要求：大专学历以上 + 年龄要求：38岁以内 ❤️🩹 工作地点：越南居家（远程） ❤️🩹 薪资待遇 : 25K-45K + 绩效 (具体面谈) ❤️🩹 工作时间 : 9休4 单休（需值夜班） ❤️🩹 试用期间：2个月 🇵🇪 岗位职责： 1. 负责公司核心业务系统的部署、监控、维护和优化,确保系统 7x24 小时高可用;通过运维监控工具(如 Zabbix、Nagios、Prometheus 等)对服务器、网络、数据库、应用进行全天候监控,通过日志…
😉😉😹😻😼😼😉😉 #日本大阪 💕DBA ❤️❤️工作职责 1、負責公司数据库架构规划、容量规划、系统调优； 2、建立和维护数据库高可用集群及监控和备份恢复机制，提高服务运行质量； 3、线上生产数据库的性能分析与调优、故障排错，保证数据库稳定运行及数据安全； 4、数据库审计以及数据库用户权限管理； 5、负责数据库的sql语句编写、审核、优化，制定数据库开发规范文档，能深度解决产品运行效 率，数据存储模型以及读写效率等问题； 6、数据库相关技术的深入研究； 职位要求: 1、5年及以上MySQL DBA实际工作经验，区块链 , 金融行业 优先； 2、熟悉MySQL常见存储引擎以及优化策略、运行机制和体系架构； 3、熟悉MySQL性能优化、SQL编程调优技术，对数据库体系架构与原理有深入研究； 4、熟悉MySQL的备份和恢复，熟悉MySQL的高可用方案； 5、熟悉Linux/Unix操作系统，熟悉任一种或多种脚本语言，比如P…
😉😉💥🔥🔆😉😉 🔆 🔴🔴 Web后端工程师 【Java+Go】 ⭐️海外集团-游戏研发🥐 💯福利好-月休🚩天 📌地点：第三国远程 薪资 ：25k-40k CNY，常白班 语言需求 : 中文 国籍 ：不限 办公地点： 第三国远程 🔽岗位职责： 1、参与公司项目及产品后端开发，按照需求文档完成系统设计与编码实现； 负责系统功能模块的开发、测试与优化； 2、分析并解决开发过程中的技术问题，持续提升系统性能与稳定性； 3、参与系统架构优化及技术选型，推动技术升级（包括 Java / Golang 技术栈）； 4、配合团队完成项目交付，保障开发进度与质量。 🔽任职要求： 1、本科及以上学历，计算机相关专业优先，5年以上后端开发经验，熟悉软件开发流程； 2、至少熟悉 JAVA和Golang 2种语言开发，有 Go 项目经验者优先； 3、熟悉面向对象设计思想，对 OOP、AOP 有较深入理解； 4、熟练掌握主流 Ja…
#前端 #web #远程 #长期远程 ♈️长期远程♈️长期远程♈️ 🇵🇳（远程办公/不限制地区）🥰🟢 #远程 前端工程师 😆 办公地点：远程办公//不限制地区 😆 薪资范围：20K-30K（具体面谈） 😆 上班时间：9休4 单休 😆 公司项目：游戏项目 😉😉任职要求： 👉1.5年以上的前端/WEB开发经验 👉2. 熟悉 TypeScript, HTML5、CSS/CSS3、JavaScnipt 物件导向，熟ES5/6/7语法 👉3.熟悉 Vue3 + Vite，掌握 Vue3 生态系，了解并使用Pinia、Vue Router、SPA、SSR 架构 👉4.使用过Node.js、NPM和Webpack且有一定程度的了解 👉5.具备 npm、yarn、pnpm,nvm 操作经验 👉6.具备串接后端 API及 WebSocket经验 👉7.具备跨浏览器、各移动端的前端开发经验 👉8.…
😉😉😹😻😼😼😉😉 #远程UI 薪资范围：15k-20k 工作时间：试用期9小时月休4 #岗位要求： 1. 男女不限， 21-35岁，大专及以上学历； 2.工艺美术相关专业毕业，具有良好的美术基础和审美能力； 3.熟练使用Photoshop、Flash、IIIustator等常用设计制作软件工具,，了解Dreamwear和Div+css等，有设计经历者优先； 4.积极肯干，吃苦耐劳；具有创新精神及团队协作精神；责任心强，还有良好的沟通能力； 工作职责： 1. 负责公司的站内外广告、图片、动画、海报、logo及网页的设计制作； 2．认真做好公司各类图片信息和主题资料的收集、整理、归档工作； 3．协助网站编辑、网站优化推广专员进行网站专题和网站美化工作； 4．完成公司、部门领导交办的其他事务； 😀备注：需会做动效，有棋牌，游戏相关经验 😀面试需要提供作品集 😉😉联系：@Mario1133 😉😉频道：@duidui0
😉😉😹😻😼😼😉😉 #到岗 #马来 #产品经理 ✅综合盘产品经理 ✅项目：综合包网(棋牌，电子，体育等) 新大楼上班 ✅薪资大约3万5~5万+ ✅马来签证，大小周，包吃住 😉😉联系：@Mario1133 😉😉频道：@duidui007
😉😉😹😻😼😼😉😉 #马来吉隆坡klcc附近大楼办公丨不压护照 #只要马来籍的 😀产品专员 : 3500U 😀产品经理 : 5000 U 时间：10:00-19:00，单休(周六居家办公 待遇：餐房补5000马币，只外宿 项目：体育包网 中国市场 社交软件app 😉😉联系：@Mario1133 😉😉频道：@duidui007
😉😉😹😻😼😼😉😉 🍄风控产品经理 （体育、彩票 或者风控类的，一个方向就行） 🍄工作地点： 马来西亚（入职地点），可远程办公一个月后转为当地入职 ✅国籍要求： 中国、台湾、马来西亚 ✅年龄要求： 40岁以内 ✅学历要求： 本科及以上学历，计算机、金融、统计、数学等相关专业优先 负责风控产品的规划、设计与迭代，制定风控产品路线图 结合业务发展阶段，设计与优化风控策略、规则及审核流程 跟踪行业风控政策及监管动态，确保产品合规 主导风控系统需求分析，输出产品文档，推动技术团队落地实现 建立健全风控管理流程与内部制度，完善风险识别、监测、预警及处置机制 与业务、技术、运营、客服等多部门协同，推动风控体系持续优化 任职要求 年龄40岁以内，本科及以上学历 5年以上风控相关产品工作经验，有互联网金融、支付、等相关行业背景优先 熟悉数据库基本操作（如SQL查询、数据提取），能够独立完成风控报表的设计 熟悉风控业务全流程…
😉😉😹😻😼😼😉😉 #斯里兰卡岗位🇱🇰 #海外盘 🇹🇬 招聘岗位：电销主管🇹🇬 薪资待遇：3000U ++ （具体面议） 国籍：国籍不限 华人优先 性别：不限 年龄：21-40 岁之间 语言要求：中英文流利 工作时间：9小时，月休4 上班时间：10am-7pm（科伦坡时间） 试用期：三个月 工作地点：斯里兰卡（科伦坡） 住宿餐食：包吃住 岗位要求 1、中英文流利，具备 2 年以上海外电销团队管理经验，制定各项电销团队绩效指标；具备曾管理南亚团队者（如孟加拉、印度等..）优先 2、具备优秀的跨文化沟通能力，制定各项电销团队绩效指标； 3、具有良好的现场/远程危机处理及团队激励能力； 4、具备良好的团队协作能力，具有较强的应变能力及带队能力； 5、具备管理 50 人以上的团队管理能力，接受轮休、排班； 6、有数据分析及业务汇报能力，能够进行数据统计、报表分析与绩效追踪； 具备专业知识 熟悉主流电销客服工单系统，例如： Z…
Showing the 12 most recent of 20 posts we hold for @duidui007. 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.
Citation-graph rank — 1,167,386 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“海外IT技术工作机会” (@duidui007), 2,049 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/duidui007.
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.