Channel
@HRODgz
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry
36subscribers
+13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003929447519 |
|---|---|
| Type | Channel |
| Username | @HRODgz |
| Created | Between 1 April 2026 and 29 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 4 times, most recently 13 November 2026 |
| On Telegram | t.me/HRODgz |
Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 30 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @HRyuanzai/3232 Aug 2026, 07:06 UTC | @HRODgz/125 · this entry2 Aug 2026, 07:06 UTC | 1.00 | under a minute |
| @HRyuanzai/3253 Aug 2026, 05:15 UTC | @HRODgz/127 · this entry3 Aug 2026, 05:15 UTC | 1.00 | under a minute |
| @HRyuanzai/3304 Aug 2026, 05:06 UTC | @HRODgz/132 · this entry4 Aug 2026, 05:06 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @HRyuanzai | 10 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @HRyuanzai (10–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 12 comparable posts for this entry, running 2 August 2026 to 11 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @HRyuanzai. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Oct 2026, 06:34 | 36 | +1 |
| 12 Oct 2026, 23:19 | 35 | -1 |
| 18 Sept 2026, 02:20 | 36 | +4 |
| 9 Sept 2026, 17:18 | 32 | +2 |
| 30 Aug 2026, 19:34 | 30 | +1 |
| 23 Aug 2026, 03:57 | 29 | +3 |
| 14 Aug 2026, 16:25 | 26 | +2 |
| 11 Aug 2026, 10:17 | 24 | no change |
| 7 Aug 2026, 14:17 | 24 | +1 |
| 7 Aug 2026, 13:45 | 23 | first reading |
20 posts held, back to 29 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
SEO专员 👥 招聘人数：若干 📍 工作地点：泰国（TH） 🕒 工作时间：10–12 小时制 / 月休 2–4 天（具体时间视情况而定） 💰 薪资待遇：15K – 20K RMB（面议） ⚧️ 性别：不限 👤 年龄：35 岁以下 🎓 学历：计算机相关专业毕业或具备相关经验 🌏 国籍：中国籍 🗣 语言要求：中文 🔎 岗位需求 不要小白 熟悉主流编程语言，对建站有深入理解，具备站群经验（操控上百站群经验优先） 熟悉百度和谷歌排名规则，掌握 SEO 手段，了解黑帽与白帽的差别 熟悉多种 SEO 推广方式，了解黑帽手法优先 能熟练应用快照劫持、寄生虫程序等方法获取定向流量 懂技术或具备一定技术能力，能结合 SEO 使用 具备 SEO 团队管理及搭建经验，学习能力与抗压能力强，能高效完成领导交代任务 🛠 岗位职责 负责公司网站在主流搜索引擎的自然排名优化，提高流量 分析并总结竞争对手 SEO 方法，合理运用提升效果 结合流量统计工具…
风控质检专员 👥 招聘人数：10 名 📍 工作地点：SLK 🕒 工作时间：9 小时制（月休 4 天）班次：9-18 / 14-23 💰 薪资待遇：10K – 12K RMB + 绩效 ⚧️ 性别：不限 👤 年龄：35 岁以下 🎓 学历：不限 🌏 国籍：不限（缅甸、福建、山东、河南敏感地区不要） 🗣 语言要求：中文流利 🔎 岗位需求 福建、山东、河南敏感地区不要 熟悉办公软件，会基本函数 思维逻辑清晰，抗压能力强 需有风控/质检经验，不要小白 🛠 岗位职责 对风控作业进行抽检，查错纠错 通过大数据分析，及时发现问题并预警 具备较强的学习与执行能力，能举一反三
接收完美的 心碎人事伙伴 OD体育给你福利待遇，提成拉满！！！ 业态动荡，招聘处境维艰。我愿接济1-2名完美的女招聘（19-25岁） 求职联系：@Yuanzai_0124
曼谷居家办公 管住不管吃，天推资源 小白有经验的都可以接受，1w底薪 +高额提成（团队也可可要） 投递联系：@Yuanzai_0124
推广专员 👥 招聘人数：若干（团队可入职） 📍 工作地点： 曼谷居家办公 🕒 工作时间：12 小时制 / 月休 2 天 💰 薪资待遇：试用期 2 个月 10000 RMB + 绩效 + 提成；转正 10000 RMB + 绩效 + 提成 ⚧️ 性别：不限 👤 年龄：21 岁以上 🎓 学历：不限 🌏 国籍：不限（中国优先） 🗣 语言要求：中文 🔎 岗位要求 接受国内小白，工作态度端正 能吃苦耐劳，具备一定情商，会聊天，对体育有一定爱好 认真负责、勤快肯努力、有上进心，服从管理 思维清晰，能灵活应变，善于沟通，抗压能力强 具有良好的沟通协调能力与高度的责任心 🛠 岗位职责 根据公司平台进行渠道扩展，利用网络及其他渠道发展会员 满足客户需求并及时推介公司最新活动 负责新客户开发与老客户维护
泰国大量需要人 推广，运营，客服，红利，高级测试工程师，数据分析，多个岗位可选，工作轻松，福利待遇优厚，欢迎咨询。 投递联系：@Yuanzai_0124
远程调研专员 👥 招聘人数：2 名 📍 工作地点：远程办公（YC，中国、马来、越南、老挝、缅甸） 🕒 工作时间：9 小时制 / 月休 4 天（白班/三班倒） 💰 薪资待遇：970 – 1390U（底薪+提成） ⚧️ 性别：不限 👤 年龄：20 – 33 岁 🎓 学历：不限 🌏 国籍：中国、台湾、越南、马来、缅甸（需中文十分流利，福建、东北、山东、河南除外） 🗣 语言要求：中文 🔎 岗位需求 2年以上工作经验，其中包括1年以上BC行业用户体验、产品等经验（财务出入款经验不计入）；或2年以上工作经验，有1年左右产品调研、市场调研、问卷调研等行业经验 敏锐的观察力，能从多个相似产品或资料中发现差异 良好的产品思维与逻辑思考能力，能将调研信息结构化整理 优秀的文档输出能力，能清晰呈现调研结果和观点，有公司/政府汇报文档经验者优先 强烈的学习成长欲望 良好的团队合作能力，有BC活动策划经验者优先 熟悉体育/电竞、真人、彩票、电子/棋牌
远程平台体验专员 👥 招聘人数：5 名 📍 工作地点：远程办公（YC，中国境内） 🕒 工作时间：9 小时制 / 月休 4 天（白班/三班倒） 💰 薪资待遇：970 – 1390U（底薪+提成） ⚧️ 性别：不限 👤 年龄：20 – 33 岁 🎓 学历：不限 🌏 国籍：中国籍（福建、东北、山东、河南除外，需在国内远程办公） 🗣 语言要求：中文 🔎 岗位需求 大专及以上学历，专业不限 热爱互联网/游戏/娱乐平台，对用户体验敏感 有1年以上平台相关工作经验（如客服、运营、测试、产品助理等）优先 熟悉账户、支付、前后台操作流程等平台功能 具备良好的观察力、逻辑思维和问题分析能力 会使用基础办公工具，能撰写体验反馈或优化建议 🛠 岗位职责 深入体验平台产品，发现操作不便、流程复杂等用户体验问题 编写体验反馈报告，提出具体改进建议 协助体验测试及数据收集工作，关注用户使用习惯 跟进已提体验问题的优化落地情况 定期整理平台体验痛点，参与
曼谷，25-31岁的推广，有经验或者小白都可以，团线，1万底薪加提成，管住不管吃，不要外宿的 天推 投递联系：@Yuanzai_0124
高级测试工程师 👥 招聘人数：1 名 📍 工作地点：泰国（TH） 💰 薪资待遇：30K – 45K RMB + 绩效 ⚧️ 性别：优先男，女优秀可考虑 🌏 国籍：中国籍 🔎 岗位需求 5年以上项目操作经验，有体育类、直播类测试经验者优先 Web 和 App 类测试经验丰富，熟知 B/S、C/S 软件特点和测试方法 测试思维缜密，能够全方位分析需求并设计测试用例 具备一定的产品思维，能够快速认知同类产品优劣势并提出独到论点 熟练使用抓包工具，能快速定位问题端口及相关接口文档 熟练使用自动化工具，具备快捷自动化思维 熟练使用主流性能测试工具，能分析性能测试报告并提出整改方案 熟练输出测试文档，具备良好的测试计划与报告习惯，能分析 bug 趋势图 具备项目管理和团队管理经验，能准确分析潜在项目风险与交付风险 🛠 岗位职责 完成日常项目迭代任务，及时输出测试报告和 bug 清单 完成临时任务，包括紧急需求、渠道包测试、上架包测试、…
📢 泰国职能岗位持续招聘 💼 多个岗位可选，工作轻松，福利待遇优厚，欢迎咨询。 📩 简历投递：@Yuanzai_0124
数据分析专员 👥 招聘人数：2 名 📍 工作地点：泰国（TH） 🕒 工作时间：9 小时制 / 月休 4 天 💰 薪资待遇：2080U – 2500U ⚧️ 性别：优先女 👤 年龄：20 – 35 岁 🎓 学历：大专 🌏 国籍：中国籍、马来西亚籍、越南籍（非河南、山东、福建） 🗣 语言要求：中文读、听、写佳 🔎 岗位需求 大专及以上学历优先，中文沟通流畅 熟练使用 Excel，掌握函数、数据透视表、Power Query 等工具 具备良好的数据分析能力、逻辑思维能力及数据敏感度，能够独立完成数据分析并形成结论 熟悉数据分析方法，能够从数据中发现问题并提出可执行的优化建议 工作认真细致，责任心强，具备良好的沟通协调能力和团队合作意识 具备较强的学习能力，能够快速理解业务逻辑及数据口径 🛠 岗位职责 负责数据的收集、整理、统计及分析，建立周度及月度数据报表 根据业务需求，独立完成活动分析、用户分析及专题数据分析，并输出分析报告 …
Showing the 12 most recent of 20 posts we hold for @HRODgz. 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.
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.
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 20 October 2026 — this entry's latest reading, not the date you are reading this.
“海外远程工作资讯” (@HRODgz), 36 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/HRODgz.
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.