Telegram RegisterThe public register of Telegram
Telegram profile photo for Betx集团【官方直聘】

Channel

Betx集团【官方直聘】

@CMHRshuxin

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

1,391subscribers

+51 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001157336270
TypeChannel
Username@CMHRshuxin
CreatedBetween 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/CMHRshuxin

Growth

1,3401,3911,365.57 August 2026 — 1,340 subscribers7 August 2026 — 1,340 subscribers9 August 2026 — 1,358 subscribers13 August 2026 — 1,373 subscribers16 August 2026 — 1,391 subscribers7 August 202616 August 2026
5 measurements spanning 10 days, net +51. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,332–1,399 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 16:341,391+18
13 Aug 2026, 00:041,373+15
9 Aug 2026, 20:111,358+18
7 Aug 2026, 02:161,340no change
7 Aug 2026, 02:081,340first reading

Engagement

20 posts held, back to 9 July 2026the 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 · 30 days
43.1%
avg views ÷ 1,391 subscribers
Avg views / post
600
14 posts measured
Reaction rate
0.356%
reactions ÷ views · ER floor
Posts in window
14
of 20 held

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 14 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (9 July 20266 August 2026)
Views total8,394
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 02:16 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.

Reaction mix

7 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
685.7%
🥰114.3%

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 5 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 7reactions 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 9 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.

Recent posts

4 Aug 2026, 10:46 UTC422 viewsread 7 August 2026

签证专员 非中国籍 非马来籍 非缅甸籍 小白可以教,要聪明伶俐的

3 Aug 2026, 06:59 UTC622 viewsread 7 August 2026

项目中心 • 资深安全架构师 : 1人 项目中心 • 项目经理: 1 IT信息部 • 云桌面工程师: 2人 • 网路安全工程师 : 2人 • 网络安全培训专员 : 2人

29 Jul 2026, 07:28 UTC889 viewsread 7 August 2026

💟💟💟花自向阳开,人终往前走,不要站在雾里,不要执着没有意义的人和事,赚钱就好,其他都俗。💟💟💟 #BTY集团 🅱️ 🌳Bsports|六月春日🌷热招中,万物生长,你也该发光了💫 😗⚡️🇾🇹 愿各位暴富 🇾🇹⚡️😗 🤓😗🤓 Java工程师 (远程) 产品经理专员 资深安全架构师 运维工程师 活动策划专员 风控专员 运营专员/组长/主管 ➡️PMO(项目经理) ➡️网络安全工程师 ➡️云桌面工程师 ➡️产品经理 ➡️Golang工程师 ➡️测试工程师 ➡️质检主管 ➡️质检专员 ➡️审计专员 ➡️泰国籍法务助理 ➡️运营主管 ➡️操盘主管 ➡️市场策划 🇮🇪🇮🇷🇭🇹🇭🇰 产品经理:1位 Golang工程师:1位 测试工程师:1位 Java工程师 产品经理专员 资深安全架构师 运维工程师 活动策划专员 PMO(项目经理) 网络安全工程师 云桌面工程师 🇮🇪🇮🇷🇭🇹🇭🇰 🇸🇭🇱🇨🇹🇼 产品经理:1位

29 Jul 2026, 07:19 UTC558 viewsread 7 August 2026

岗位需求: 市场策划 上班时间:9休6 薪资待遇: 面议,最高1万美金 入职地点: 泰国/菲 岗位职责: 负责每天筛选、审核和策划可上线的预测事件,包括: 国际政治(美国大选、国际关系) 体育赛事(世界杯、NBA、电竞) 财经(美联储、比特币、黄金、AI 公司) 科技(OpenAI、Apple、Tesla 等) 娱乐(电影、明星、游戏) 社会热点(重大新闻、突发事件) 目标是保证平台每天都有足够的新鲜、高质量市场,持续吸引用户参与交易。 任职要求: 本科及以上学历。 3 年以上互联网平台运营经验 有预测市场、Web3、交易所、金融产品、博彩平台或互联网社区运营经验者优先。 熟悉用户增长、活动运营、数据分析及运营体系建设。 熟练使用 Excel、SQL、Google Analytics、Mixpanel 等数据分析工具优先。 具备优秀的数据分析能力、项目管理能力及跨部门沟通能力。 对国际热点新闻、政治、财经、科技、体育

29 Jul 2026, 07:17 UTC468 viewsread 7 August 2026

岗位需求:操盘主管 上班时间:9休6 薪资待遇:面议,最高1万美金 入职地点: 泰国/菲 岗位职责: 负责预测市场日常运营及市场管理,确保市场运行稳定、高效。 根据国际热点事件创建预测市场,并制定市场规则、结算规则及风险控制策略。 管理市场流动性,结合用户交易情况优化市场深度及交易体验。 监控各预测市场成交量、价格波动及持仓情况,及时调整运营策略。 与产品、研发共同优化交易机制、订单系统、价格展示及结算流程。 建立市场生命周期管理,包括市场创建、审核、运营、结算及归档。 建立异常交易监控机制,识别恶意操纵市场、异常成交及套利行为,并配合风控处理。 持续研究 Polymarket、Kalshi、PredictIt 等国际预测市场产品,优化平台规则及运营策略。 输出市场运营日报、周报及月报,为管理层提供数据分析及运营建议。 任职要求: 本科及以上学历。 3 年以上交易平台、预测市场、体育博彩、交易所或金融市场运营经验。 熟悉

29 Jul 2026, 07:13 UTC474 viewsread 7 August 2026

岗位需求: 运营主管 薪资待遇: 面议,最高1万美金 入职地点: 泰国/菲 上班时间: 9休6 岗位职责: 负责预测市场平台整体运营工作,制定并执行平台运营策略,提升用户活跃度、留存率及交易规模。 根据市场热点策划预测事件,协调产品、运营、设计及研发完成上线。 制定用户增长方案,包括新用户拉新、用户留存、促活、召回等运营策略。 策划平台活动,如竞猜活动、排行榜、任务系统、奖励机制等,提高用户参与度。 建立平台运营数据体系,监控 DAU、MAU、交易人数、交易金额、留存率、转化率等核心指标,并持续优化。 跟踪国内外预测市场、Web3、金融交易平台的发展动态,持续优化产品运营模式。 协同商务团队对接合作伙伴、媒体、KOL、代理渠道,提升平台曝光及交易量。 建立运营 SOP,完善内容发布、市场审核、公告管理及用户反馈机制。 任职要求: 本科及以上学历。 3 年以上互联网平台运营经验,至少 2 年团队管理经验。 有预测市场、

28 Jul 2026, 05:11 UTC538 views2 reactionsread 7 August 2026

帮朋友招聘 远程的安卓flutter 远程前端工程师 只要一个有意向可以联系下

2

24 Jul 2026, 05:16 UTC818 viewsread 7 August 2026

😀😃后端工程师(Go) ⏰工作时长:9小时月休6 💵工资:面议 📍入职地点:泰国/马来/菲律宾-居家 岗位职责: · 搭建链上数据 Indexer、盘口 / 市场状态服务、实时事件处理管线 · 设计服务架构、缓存策略、数据模型和监控告警体系 · 在压力、延迟、可用性和一致性之间进行取舍,并能解释取舍逻辑 · 持续优化性能、可扩展性和系统韧性 · 与产品 / 合约 / 前端进行并行协作,确保版本按节奏交付 岗位要求 · 熟悉 Go 语言,理解 Goroutine、Channel、Context、并发模型基础 · 熟悉 PostgreSQL/Redis/MQ 中至少两项,并理解它们的使用场景边界 · 代码结构清晰,命名合理,能写出可维护、可阅读、可扩展的模块 · 具备 问题跟踪 → 分析 → 定位 → 解决 的基本链路思维 · 推进稳定、沟通直接、能对交付结果负责 成长路径: · 1–2 个月:成为某模块的稳定 Owner(

24 Jul 2026, 05:14 UTC671 viewsread 7 August 2026

#职位名称:测试工程师 #薪资待遇: 面议 #工作时间:9小时月休6 #工作地点:泰国/马来/菲律宾-居家 #岗位职责: 1 根据需求文档和设计文档,制定测试计划,设计测试方案、测试用例和测试脚本。 2 评估测试范围,确定测试重点和风险,确保覆盖关键功能和业务场景 3 执行功能测试、性能测试、兼容性测试、回归测试等不同类型的测试,确保产品达到质量标准。 4 使用手动或自动化测试方法,验证产品功能的正确性、稳定性和一致性 5 记录并追踪测试结果,确保问题及时得到解决。 #任职要求: 1 计算机科学、软件工程或相关专业本科及以上学历。 具备5年以上软件测试工作经验,有复杂系统或大型项目测试经验者优先。 2 熟悉软件测试理论、流程和方法,能独立完成测试方案的设计与实施。 掌握常用测试工具,如Postman、JMeter、Selenium、Appium等。 了解主流编程语言(如Java、Python)及其在测试自动化中的应用。

24 Jul 2026, 05:13 UTC585 viewsread 7 August 2026

岗位需求:运维工程师 薪资待遇:面议 上班时间:9个小时-月休6天 工作地点:泰国/菲 居家 岗位职责: 1.规划业务系统部署架构,完善运维架构 2.推动DevOps工具链的落地实施-通过jenkins/CICD流水线实现开发,测试,上线等全生命周期管理 3.对业务系统能熟练排查、定位系统问题; 4.熟练监控系统promethues/zabbix,熟练日志系统elk,loki; 5.Linux系统运维和调优,具备主机安全知识及实践; 6.具备编写Python或golang或Shell脚本完成日常工作的能力; 7.维护常见中间件软件部署、配置、优化,MQ、Redis、Tomcat,Nginx等; 8.负责领导安排的其他工作要求。 任职要求: 1.计算机相关专业,全日制统招大专及以上学历(学历硬性要求),全日制本科学历以上优先; 2.推动DevOps工具链的落地实施-通过jenkins/CICD流水线实现开发,测试,上线等全生命

Showing the 12 most recent of 20 posts we hold for @CMHRshuxin. 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

Citation-graph rank — 1,004,119 of 1,481,306entries 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

Named by 3 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.

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.

Appears in Telegram’s recommendations for other channels

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.

迪拜 东南亚求职招聘
@Dubaiqzzp · 87,693
Telegram ranks this channel #32 of 64 here — alongside 63 others — read 17 August 2026
找工作|招聘|人事【博牛招聘】
@bnzhaopingmnl · 65,234
Telegram ranks this channel #53 of 84 here — alongside 83 others — read 15 August 2026
TG招聘|求职|人才聚集地✳️
@XCRLZP · 124,868
Telegram ranks this channel #69 of 82 here — alongside 81 others — read 13 August 2026

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.

Cite this entry

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 August 2026 — this entry's latest reading, not the date you are reading this.

“Betx集团【官方直聘】” (@CMHRshuxin), 1,391 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/CMHRshuxin.

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.