Channel
@xiaobeivvdd
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,159subscribers
+17 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001795099508 |
|---|---|
| Type | Channel |
| Username | @xiaobeivvdd |
| Created | Between 1 December 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/xiaobeivvdd |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 15:26 | 2,159 | +16 |
| 7 Aug 2026, 09:40 | 2,143 | +1 |
| 7 Aug 2026, 05:31 | 2,142 | first reading |
16 posts held, back to 23 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 2 pagesof 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 2 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 16 (23 July 2026 – 6 August 2026) |
| Views total | 6,809 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:55 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 2 of the 16 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 16 most recent posts we hold, published 23 July 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.
🍀曼谷居家远程： 1、品牌经理（游戏） 2、行政助理 台/马籍 3、测试工程师/总监/主管 4、产品经理 5. WEB前端架构/前端主管/总监 6.高级web前端-前端架构 7. 项目经理 8. Java架构师 9、Java主管 10、高级架构师（Java / 分布式系统） 11、运营专员/主管/数据运营 12、企业培训专员/组长 外籍 13、HRBP专员/HRPB组长/主管 外籍 🍀中/台/马（第三国长期远程） 数据库专家 ｜大数据DBA（数仓方向） ｜ 业务监管DBA DBA运维 ｜ 中高级Go/区块链Go/钱包Go/交易所Go 架构师（AI） ｜ 架构师（Golang） ｜SEO白帽/黑帽 运维平台后端开发工程师（Go/微服务） ｜SRE运维 Go高并发系统架构师 ｜资深Java 中高级React Native开发（Android） ｜AI运维工程师 中高级Go业务开发 ｜中高级Go游戏…
亚美尼亚开放岗位： 高級前端/Go/視頻剪輯/ 非中國籍的—-》UX /會CRM的運營 1、运营总监 2、产品运营专员 3、客服助理，2000U，30以内。中国/马来籍。 4、推广专员 5、投放专员（马来/中国籍） 求职联系：@Daisymakati
急招曼谷宿舍办公php 一个位置 求职联系：@Daisymakati
olang工程师 工作时间：10小时，月休4 工作地点：菲律宾居家 薪资待遇：30~40K + 房补 + 餐补 + 项目奖金 工作内容：负责公司大型站群系统的开发和管理 相关经验：有CMS系统开发经验者优先 岗位职责 1. 负责公司CMS（内容管理系统）、门户网站矩阵及SaaS化内容服务平台的核心模块设计与Go语言后端开发。 2. 推进CMS系统的改造与高并发架构优化，满足千万级PV、高并发访问及海量数据存储的稳定性需求。 3. 能够设计灵活的内容模型（如自定义字段、多语言支持、分类体系）、权限管理（RBAC）及工作流引擎。 4. 设计并实现CMS插件化机制、模板引擎解析及API开放平台（如OpenAPI等），方便第三方系统集成与二次开发。 5. 对接各大CDN加速服务、对象存储（OSS）、搜索引擎（Elasticsearch）及第三方营销组件。 6. 编写高质量代码及技术文档，保障系统安全（防SQL注入、XSS攻击等），进…
❤1
职位：远程UI / 美术 / 视频制作 🎨 负责设计符合品牌形象的线上展示内容，包括社交媒体（Facebook、Instagram 等）的配图、海报及设计工作。 📄 根据运营需求，完成活动落地页及 Banner 广告图的设计制作。 💻 技能要求： - 熟练操作 Photoshop、Illustrator 等设计软件； - 具备 AI 绘图能力或手绘功底者优先。 👁️ 审美能力：具备良好的色彩感知与布局规划能力，能精准把握品牌调性。 ⚡ 工作效率：线上沟通顺畅，对待修改需求耐心细致，能够按时交付，杜绝拖延。 📚 经验要求：具备新媒体设计经验者优先。 求职联系：@Daisymakati
岗位：运维业务工程师（非中国籍） 薪酬范围：25k起 工作地点：BGC 岗位职责 1. 负责公司服务器及云资源（计算、存储、网络）的日常运维管理 2. 参与云服务器资源的申请、部署、扩容、缩容及下线 3. 保障线上系统的稳定性与可用性，配合处理日常运维问题 4. 协助技术团队完成环境搭建、配置调整及版本发布支持 5. 负责服务器、云资源的基础巡检、监控及问题跟进 6. 维护运维相关文档、资源台账与配置记录 --- 任职要求 1. 本科及以上学历，计算机或相关专业优先 2. 2 年及以上基础运维或服务器管理相关经验 3. 熟悉 Linux 系统，掌握常见运维操作与排查方法 4. 熟悉主流云平台（阿里云 / 腾讯云 / AWS 等）的基础使用 5. 具备良好的责任心与沟通能力，执行力强 --- 备注（重点说明） • 具备云服务器采购、资源选型或成本评估经验者优先 • 有云资源计费模式、续费、扩容策略相关经验者优先 • 对资源使用率…
职位需求更新（可远程）： 急召：cocos creator 学历：大专以上 薪资：25k内 待遇：出差按照到岗薪资算，3000日元/日补贴，提供住宿 补充：需要远程+出差（出差日本，办理3-5年旅游签证）
马尼拉岗位： DBA 技术支持 java 服务端开发 技术总监 测试总监 高级运维 高级网络工程师 dba值班 项目管理 PMO 用户界面设计师 高级投资经理 前端产品经理 游戏产品经理 flutter（移动客户端专家） 资深测试 战略运营总监 资深UI 设计师 资深真金游戏策划 资深游戏前端工程师 高级游戏厅前端工程师 高级游戏后端工程师 ui设计师 AI应用开发工程师 求职联系：@Daisymakati
岗位名称：远程产品经理 薪酬范围：25k起 岗位职责： 1. 负责公司旗下海外体育产品； 2. 协调运营、UI、测试、研发团队，有效推进产品的实现与交付； 3. 根据公司及用户需求，结合市场调研情况，进行产品定位和发展规划； 4. 了解海外竞争对手同类产品功能及特色，跟踪其产品功能进展，定期提交竞争对手产品功能分析报告，并结合本公司产品定位，有针对性地提交改进建议； 5. 跟踪产品数据，汇总产品BUG和意见反馈，提出优化产品体验的思路和改进方案并推进落地，持续改善产品的用户体验；把控产品版本更新和迭代节奏。 任职要求： 1. 大学本科以上，3年以上移动互联网C端产品经验，有独立从0到1的项目经验； 2. 熟练使用产品相关工具，可以快速将用户反馈和需求落实成产品原型； 3. 优秀的原型交互设计能力，熟悉产品流程图绘制以及产品需求文档的撰写； 4. 有成熟的产品数据分析经验，擅长利用数据分析改善产品体验，有自己的产品思路和理论，…
远程TM招聘 Devops工程师 海外内容产品经理（爽文/短剧/短视频剧集方向） 产品增长经理 初级运营 项目助理 生成式广告素材专家｜P0（紧急/高） 高级产品经理（pmo方向） 内容运营 AI内容编辑 （绿色） AI内容编辑（成人） SEO增长负责人（内容/媒体/视频资讯方向 年薪60–70万元 ） AI 业务分析专员｜P1（中） 求职联系：@Daisymakati
岗位名称：运营负责人 办公时间：周末双休 工作地点：远程（优先考虑可到马来西亚工作） 薪资范围：面议 工作强度：创业项目，初期约60小时/周 团队规模：管理1名运营专员，协作8人团队 项目方向: 负责 AI 成人内容平台的整体运营，涵盖 AI 文字、图片、视频等内容产品，推动平台用户增长、创作者生态建设及商业化发展。 工作内容: 1. 渠道增长（Growth） *负责多个推广渠道的投放及优化，制定增长策略，持续提升 ROI、CTR、CVR、CAC 等核心指标，管理推广预算及渠道合作，并不断测试及优化广告创意、文案和落地页。 *要求具备 3年以上渠道推广或增长运营经验，熟悉 CPS、CPA、CPM 等推广模式，拥有成功推广案例及具体数据成果，能够独立分析数据并快速制定优化方案。 2. 创作者生态（Creator Operations） *负责建立创作者招募及激励机制，拓展优质创作者资源，维护创作者社群，与重点创作者建立长期合作…
曼谷宿舍办公php 30-40k 一个位置 求职联系：@Daisymakati
Showing the 12 most recent of 16 posts we hold for @xiaobeivvdd. 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,108,198 of 1,169,250entries 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 3 seed channels' Telegram-generated recommendation lists 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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“技术全球招聘求职中心” (@xiaobeivvdd), 2,159 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/xiaobeivvdd.
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.