Telegram RegisterThe public register of Telegram
Telegram profile photo for 新💜马💜日💜泰💜菲💜柬💜越…海外IT技术招聘

Channel

新💜马💜日💜泰💜菲💜柬💜越…海外IT技术招聘

@CQM78

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

7,516subscribers

+25 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001888661175
TypeChannel
Username@CQM78
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/CQM78

Growth

7,4857,5167,500.57 August 2026 — 7,491 subscribers7 August 2026 — 7,491 subscribers10 August 2026 — 7,499 subscribers14 August 2026 — 7,485 subscribers17 August 2026 — 7,490 subscribers20 August 2026 — 7,485 subscribers24 August 2026 — 7,486 subscribers26 August 2026 — 7,490 subscribers30 August 2026 — 7,506 subscribers5 September 2026 — 7,516 subscribers7 August 20265 September 2026
10 measurements spanning 29 days, net +25. 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 7,480–7,521 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 13:007,516+10
30 Aug 2026, 08:427,506+16
26 Aug 2026, 22:337,490+4
24 Aug 2026, 05:387,486+1
20 Aug 2026, 07:117,485-5
17 Aug 2026, 12:277,490+5
14 Aug 2026, 00:277,485-14
10 Aug 2026, 17:137,499+8
7 Aug 2026, 10:117,491no change
7 Aug 2026, 09:477,491first reading

Engagement

135 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.26%
avg views ÷ 7,516 subscribers
Avg views / post
320
98 posts measured
Reaction rate
0.12%
reactions ÷ views · ER floor
Posts in window
99
of 135 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 15 of 98 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 28 August 2026
Posts held135 (6 August 202628 August 2026)
Views total31,378
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 22:30 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

8 reactions across 8 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8100.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 20 of the 135 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 135 most recent posts we hold, published 6 August 2026 to 28 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

28 Aug 2026, 15:07 UTC139 viewsread 28 August 2026

#马来西亚新山 宿舍办公 🩷 高级活动运营 🩷 高级产品运营 🩷 CMO 🩷 COO

28 Aug 2026, 12:57 UTC193 views1 reactionsread 28 August 2026

💥💥💥💥💥 海外集团-游戏研发 福利好-月休🚩天 地点:在第三国远程 💫 游戏设计副总监 薪资 :底薪12,000美元, 根据经验与能力提供具有竞争力的薪酬及激励方案。 语言需求 : 中英文 性别 :不限 国籍 :中国或者台湾 办公地点: ✨ 在第三国远程 【不接受在中国国内远程】 👌岗位职责: 1、负责公司B端游戏产品的整体设计策略和方向,确保产品具有创新性和市场竞争力, 2、主导游戏系统、玩法规则、界面交互、数值平衡等核心设计工作,指导团队完成高质量的设计方案, 3、参与产品立项、策划、上线及迭代过程,确保设计方案落地并符合运营需求, 4、带领和管理游戏设计团队,制定团队工作标准、流程及成长计划,提升团队整体能力, 5、分析行业趋势、竞品数据和用户行为,提出前瞻性设计优化建议, 6、推动AI技术在B端游戏设计中的应用,包括玩法智能化、用户行为预测、个性化推荐及数据驱动的设计优化, 7、确保

1

28 Aug 2026, 12:11 UTC205 viewsread 28 August 2026

💥💥💥💥💥 【招聘】游戏客户端开发工程师 薪酬范围:15-26k 备注:长期远程 岗位职责: 负责公司游戏客户端的开发、迭代及日常维护; 使用 Cocos Creator 进行游戏客户端功能开发、UI实现、性能优化及问题排查; 负责游戏客户端与服务端接口对接,以及相关业务逻辑开发; 负责 Android / iOS 平台适配、打包、发布及原生功能接入; 处理客户端兼容性、性能、崩溃、网络等相关问题; 配合产品、UI、后端完成游戏功能快速迭代和上线。 任职要求 熟练使用 Cocos Creator,有完整游戏项目开发经验; 熟练掌握 TypeScript / JavaScript; 熟悉 Vue 等前端技术栈; 熟悉 Android 原生开发,能够处理 Gradle、SDK接入、打包、权限、兼容性等问题; 熟悉 iOS 原生开发,能够使用 Xcode,处理打包、签名、SDK接入及相关问题; 熟悉 Cocos 与 Androi

28 Aug 2026, 10:07 UTC245 viewsread 28 August 2026

💥💥💥💥💥 #马来吉隆坡-宿舍办公 💫 高级运维 💫 值班运维 💫 高级java(大数据方向) 💫 产品 💫 UI 🎀备注:35岁以下 熟悉AI优先 30-50k #8小时单休 👍求职热线:@UX718718

28 Aug 2026, 09:30 UTC243 viewsread 28 August 2026

💥💥💥💥💥 #马来西亚吉隆坡 招聘岗位:运营专员/项目专员 *1位 薪资3500-4000美金 核心背景:必须是马来西亚本地人,且必须具备线上德州扑克(Online Poker App/Platform)的真实运营或项目管理经验。 业务能力要求: 熟悉线上德州的俱乐部/联盟模式、抽水/返水机制、赛事(MTT/SNG)排期与日常运营配置; 具备良好的项目管理(Project Management)能力,能对接技术团队(Golang/Cocos)推动需求上线; 人选特征: 中文必须流利(能与中国籍高管及技术沟通),EQ 极高,懂向上管理与团队润滑; 办事圆滑、配合度高,懂扑克圈文化与逻辑

28 Aug 2026, 09:07 UTC242 viewsread 28 August 2026

💥💥💥💥💥 #马来吉隆坡 🩷 Java 开发工程师(远程/驻场) 支付平台经验(熟悉USDT支付流程) 💫 产品经理(远程/驻场) 支付平台经验(熟悉USDT支付流程) 🩷 安卓逆向工程师(远程/驻场) 银行项目经验优先 办公模式: 💫可长期远程办公-不限地区 💫可短期远程2个月,再去马来入职现场办公 #远程薪资:不超过30k #到岗薪资:30-50k

28 Aug 2026, 08:47 UTC233 viewsread 28 August 2026

💥💥💥💥💥 #职位:高级技术架构师(Go方向)需要技术实力+管理能力 #薪资:30K-50K 成人项目|视频面试|入职不用个人信息 不限地区|人在国内或者海外都可以 岗位职责 1.负责公司核心系统的技术架构设计、评审与持续演进,结合业务发展制定可落地的技术方案。 2.深度参与Go核心系统及关键模块研发,能够承担核心代码编写、代码评审、性能优化和复杂问题排查。 3.接管现有产品及技术系统,梳理系统架构、代码资产、服务依赖、数据链路、基础设施和发布流程,建立完整的技术架构视图。 4.对原有Go、PHP或Java系统进行技术分析,识别架构缺陷、历史技术债、性能瓶颈和稳定性风险,制定分阶段治理方案。 5.负责高并发、高可用、分布式系统的架构设计与优化,提升系统的稳定性、扩展性、安全性和可维护性。 6.负责关键技术选型及技术方案评审,在业务交付速度、系统稳定性、技术成本和长期演进之间作出合理判断。 7.参与P0/P1线上故

28 Aug 2026, 08:45 UTC219 viewsread 28 August 2026

💥💥💥💥💥 #职位招聘:游戏主策划 / 资深系统策划 #薪资范围:25K - 30K 成人项目|视频面试|入职不用个人信息 不限地区|人在国内或者海外都可以 【岗位职责】 负责整体游戏产品方案、核心玩法循环(Core Loop)及游戏设计文档(GDD)的撰写与落地。 搭建游戏核心数值框架、经济系统及长线成长体系,确保产品具备良好可玩性与商业化潜力。 作为视觉需求把关人,向美术外包团队清晰传达美术风格与规范,并负责外包资产验收监修。 与前端(Unity)和后端主程深度配合,确保玩法、网络逻辑及数值实现不走样。 从前期小型网络游戏的快速验证,到后期向大型网络手游平滑升级的演进过程中,持续迭代产品设计方案。 【任职要求】 大专及以上学历,5年以上游戏行业策划经验,至少完整经历过1-2款上线网络游戏(非纯单机)的全流程研发。 具备极强的逻辑思维能力与文档编写能力,能熟练输出高质量的GDD、系统案及数值平衡表。 对Unity客户端与

28 Aug 2026, 08:44 UTC211 viewsread 28 August 2026

💥💥💥💥💥 #马来西亚吉隆坡 🩷 产品经理 🩷 数据分析 🩷 项目管理 🩷 AI 转型落地经理 🩷 AI 视频动画师 🩷 市场扩展 🩷 商务 只限女生(非中国籍) 内容编辑 🩷 UI/UX设计师 🩷 用户增长运营 🩷 社交媒体运营 🩷 社群运营 🩷 视频剪辑 🩷 品牌运营 🩷 活动策划 🩷 线上客服 只限男生 (马来籍优先) 🩷 风控专员 只限男生(马来籍优先) 🩷 支付专员 只限女生(马来籍优先)

28 Aug 2026, 08:41 UTC198 viewsread 28 August 2026

💥💥💥💥💥 #泰国曼谷居家办公 职称:中高级java 年纪40内 薪资 30-50 有租房补助餐补 要求无bc经验,交易所经验优先

28 Aug 2026, 08:41 UTC207 viewsread 28 August 2026

风控专员 国籍:不限 薪资:12-15K面议 工作时间:12小时月休8(两班倒) 办公:海外远程办公(中国大陆除外) 岗位职责 审核各博彩项目的客户以及注单 ; 报表分析并提供止损方案; 协助优化风控后台; 需协助相关部门解决客户疑问。 岗位要求 综合盘经验,彩票盘优先,熟悉沟通业务上的问题; 资深2年以上B端或C端风控经验 ; 熟悉电脑操作以及办公软件; 有足够的逻辑思考能力且能独自解决业务上的一些问题 ; 能建议风控后台工具的实用性; 有能力带领班次并有效协助解决组员业务上的问题。"

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

Posts edited after publishing

@CQM78 edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
12 August 2026
Most recent edit
20 August 2026

Mentions

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.

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.

DeJob—Web3招聘求职频道📮
@DeJob_official · 46,532
Telegram ranks this channel #60 of 94 here — alongside 93 others — read 27 August 2026
TG招聘|求职|人才聚集地✳️
@XCRLZP · 131,471
Telegram ranks this channel #74 of 82 here — alongside 81 others — read 13 August 2026

This channel appears in 2 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“新💜马💜日💜泰💜菲💜柬💜越…海外IT技术招聘” (@CQM78), 7,516 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/CQM78.

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.