Channel
@HRDWee
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
200subscribers
-473 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001508945122 |
|---|---|
| Type | Channel |
| Username | @HRDWee |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/HRDWee |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 18:23 | 200 | -16 |
| 16 Aug 2026, 08:15 | 216 | -433 |
| 8 Aug 2026, 09:16 | 649 | -24 |
| 8 Aug 2026, 02:32 | 673 | no change |
| 7 Aug 2026, 20:47 | 673 | first reading |
20 posts held, back to 2 June 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.
| Window | Rolling 30 days · latest post in window 3 August 2026 |
|---|---|
| Posts held | 20 (2 June 2026 – 3 August 2026) |
| Views total | 107 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 02:32 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.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 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 2reactions 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 2 June 2026 to 3 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.
财务专员 薪资：1680U - 2000U+绩效 上班地点：🇱🇰斯里兰卡 工作时间：9小时月休4天（轮班/无大夜班） #岗位职责： 1.负责⽀付渠道与公司内部⽹站的对接，维护支付渠道并合理配置资源。 2.负责支付渠道资余额控管与协调对接。 3.公司内部日常费用申请与对接。 4.公司内部客服对接支付渠道订单漏单。 5.公司内部基础风控审核提款稽核。 6.与会员对接基础支付渠道的问题。 7.与报表对接支付渠道合作规则，协助公司报表排查日常对账问题 8.日常数据整理统计。 #岗位要求 1.具有清晰的逻辑分析能⼒与计划执⾏能⼒， 2.责任⼼强，有团队协作精神，耐⼼、细⼼，⼯作态度端正 3.良好的沟通表达能⼒ 4.熟练使⽤word、excel、ppt等办公软件 5.中文或英文双语优先考虑
直播站运营主管 办公地点：斯里兰卡 薪资区间：3000-5000U（具体面议） 休假：9休6（长白班） #岗位职责 * 负责直播平台整体运营及日常管理，制定平台运营策略。 * 负责主播招募、培训、考核及激励，建立主播成长体系。 * 策划体育、电竞、游戏等直播内容及平台活动，提升用户活跃度。 * 提升平台观看人数、用户留存、礼物打赏及付费转化。 * 对接主播、公会、合作伙伴及渠道资源，拓展平台内容生态。 * 分析直播数据，持续优化平台运营效果。 * 协调产品、技术、市场等团队，推动新功能及活动上线。 #任职要求 * 3年以上直播平台运营经验，有团队管理经验优先。 * 熟悉直播平台运营逻辑，了解主播、公会及用户运营。 * 有体育直播、电竞直播、娱乐平台经验优先。 * 具备活动策划、数据分析及项目推进能力。 * 有较强的沟通协调能力及团队管理能力。 * 结果导向，能独立负责平台运营工作。
人事行政（行政业务) 工作地点：🇱🇰斯里兰卡 工作时间：9小时月休8 薪资范围：1820U - 3000U （薪资可谈） 年龄：能力决定一切 国籍：只限外籍 应聘要求： 1.熟悉办公室行政流程、文件整理、物资采购与报销等事务。 2.熟练使用Office办公软件（Excel、Word等），具良好沟通与协调能力。 3.抗压性强，责任心高，能配合团队执行任务。 4.中英文能读听写 工作内容： 1.负责办公区日常行政管理，包括物资采买、仓储盘点、住宿安排与清洁协调。 2.协助人员入离职手续办理、档案资料整理与系统录入。 3.跟进员工考勤、请假、调班、假期统计与报表整理。 4.支持人资部门执行招聘、培训、活动等行政配合工作。 5.协助处理签证、工卡、保险等相关事务。 6.负责公司公告、文件起草与公文流转。 7.维护办公区秩序，监督后勤供应及设施维护情况。 8.协助上级完成其他临时性事务。
风控专员 -组长 工作方式：远程或者菲律宾 工作时间：12小时月休2天（包含吃饭休息时间） 国籍：外籍 （中国籍需本科毕业） 远程薪资：专员试用期ˊ：9000 转正：9000+1K绩效 组长试用期14000 转正14000➕1k绩效 到岗薪资: 15000-18000➕绩效 #岗位要求 1.具备1年以上BC风控经验优先 2.熟悉中国体育/彩票综合盘风控知识优先 3.具备风险识别及分析能力 4.逻辑思维清晰，责任心强 5.能够适应轮班制度 #岗位职责 1.负责平台会员风险审核 2.监控异常投注及风险行为 3.处理风控预警及异常案件 4.协助优化平台风控策略
远程彩票客服需求10位，招完即停 需要具备彩票客服知识1年以上 要求外籍人选，非中国籍，男女不限 面试详情： 1.需要提供完整工作经验简历 2.需要提供打字测试视频（需要清晰看到打字人是本人） https://dazi.kukuw.com/ 打字测试一分钟/不少于40个
岗位：远程推广专员 薪资：底薪12转14 ➕10个点提成 年龄：40岁以下 国籍：中国优先 工作时间:9休4 1. 了解产业推广渠道，并熟悉 QQ，微信，百度，论坛，谷歌、抖音、快手，小红书 直播等网络的推广 与平台 。 2. 有高度的责任感、工作稳重。 3具备良好的学习能力、喜欢挑战和超越自我。 4.中文流利，打字速度 40 以上。 5.接服从公司管理。 1.具备一定渠道开发能力，有自己的渠道资源 愿意用心专研: 2.通过各种渠道及营销工具开发用户，完成每月业绩指标； 3.了解及搜集网络各同行及竞品的动态信息； 4.对博彩行业，有一定了解及认识。"
👀 7月招聘需求 👉【远程推广】 👉【客服专员/组长】 👉【风控专员/组长】 👉【运营专员组长】 👉【HRBP组长] 👉【hou 端工程师】 👉【AI质检】
❤1
📢招募：【HRBP组长】 国籍要求：外籍（台湾优先） 性别要求：女 年龄要求：25-40岁 语言要求：中文流利，英文加分 住宿：公司提供2～4人间宿舍 工作时间/休假：10小时/月休4 📍工作地点：菲律宾马尼拉 Solaire 🪙薪资待遇： 试用期薪资：2800U（两个月） 转正薪资：3000U 🔗岗位要求： 1.具备3年以上资深人资经验或人资组长1年以上管理经验 2.具备优秀的沟通协调及跨部门推动能力 3.能够独立分析组织问题并提出改善方案 4.具备较强的数据分析及逻辑思维能力 5.熟悉KPI、OKR、绩效面谈等管理工具优先 6.具备较强责任心、执行力及保密意识 7.熟悉员工入离职、考勤、薪资、绩效、培训等人力资源管理流程 8.具备良好的沟通协调能力及跨部门协作能力 9.熟练使用Excel、Word、PowerPoint等办公软件 🗓️岗位职责： 1.作为业务部门与管理层之间的人力资源桥梁，协助推动各项管理制度落地执…
人事行政（行政业务) 工作地点：🇱🇰斯里兰卡 工作时间：9小时月休8 薪资范围：1820U - 3000U （薪资可谈） 年龄：能力决定一切 国籍：只限外籍 应聘要求： 1.熟悉办公室行政流程、文件整理、物资采购与报销等事务。 2.熟练使用Office办公软件（Excel、Word等），具良好沟通与协调能力。 3.抗压性强，责任心高，能配合团队执行任务。 4.中英文能读听写 工作内容： 1.负责办公区日常行政管理，包括物资采买、仓储盘点、住宿安排与清洁协调。 2.协助人员入离职手续办理、档案资料整理与系统录入。 3.跟进员工考勤、请假、调班、假期统计与报表整理。 4.支持人资部门执行招聘、培训、活动等行政配合工作。 5.协助处理签证、工卡、保险等相关事务。 6.负责公司公告、文件起草与公文流转。 7.维护办公区秩序，监督后勤供应及设施维护情况。 8.协助上级完成其他临时性事务。
远程体育客服需求3位，招完即停 需要具备体育客服知识1年以上 要求外籍人远，非中国籍 面试详情： 1.需要提供完整工作经验简历 2.需要提供打字测试视频（需要清晰看到打字人是本人） https://dazi.kukuw.com/ 打字测试一分钟/不少于40个
招聘岗位： AI应用工程师 #上班地点：菲律宾 招聘国籍： 不限国籍 工作休假，10月休4 #薪资待遇： 根据能力线上谈/高薪 #工作职责： 一、AI应用落地 1.负责将ChatGPT、Claude、Gemini等AI工具导入公司各部门业务场景 2.规划并搭建AI Agent工作流，提高团队整体工作效率 3.建立企业知识库系统，实现知识沉淀与智能检索 4.设计自动化流程，减少重复性人工操作 5.推动AI技术在人资、运营、客服、财务、风控等部门落地应用 6.持续优化AI解决方案，提高业务效率及产出质量 二、系统优化与管理 • 分析各部门工作流程，挖掘AI应用场景 • 制定AI应用规范及标准作业流程（SOP） • 负责AI工具权限管理及使用培训 • 跟踪AI技术发展趋势并评估导入价值 • 建立数据反馈机制，持续优化应用效果 三、个人特质 • 对AI技术充满热情，具备持续学习能力 • 逻辑清晰，善于拆解复杂问题 • 具…
自媒体运营专员 薪资：1680USD-2100+绩效（能力优秀面议） 上班地点：🇻🇳越南--🇱🇰斯里兰卡 工作时间：9小时月休8天（长白班） #岗位职责： 1.负责账号（如抖音、快手、小红书、公众号、微博等）的日常内容发布、维护及管理。 2.制定账号增长策略，提高粉丝量及活跃度。 3.内容策划与创意： 4.策划符合品牌调性和用户需求的内容，包括短视频、图文、直播等形式。 5.跟进热点，创作高传播性的内容，提高流量与曝光度。 6.用户增长与运营：分析用户画像与需求，制定用户增长计划。 7.数据分析与优化： 8.追踪内容表现，定期整理运营数据（粉丝增长、互动量、曝光量等），并提出优化建议。 9.分析竞品动态，制定差异化策略。 #岗位要求： 1.本科及以上学历，市场营销、新媒体、传播学等相关专业优先。 2.具备1年以上自媒体运营经验，有小飞机短视频平台运营经验者优先。 3.熟悉主流自媒体平台的规则、玩法及运营工具。 4.具备内…
Showing the 12 most recent of 20 posts we hold for @HRDWee. 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 — 398,144 of 1,622,129entries 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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“官方直招🧜🏻美好生活💬” (@HRDWee), 200 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/HRDWee.
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.