Telegram RegisterThe public register of Telegram
Telegram profile photo for 🛡远程/到岗/菲律宾直招

Channel

🛡远程/到岗/菲律宾直招

@taizihryumi

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

490subscribers

+99 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002009755325
TypeChannel
Username@taizihryumi
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/taizihryumi

Topic

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 21 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 why it has no browse page of its own yet.

Growth

391490440.57 August 2026 — 391 subscribers7 August 2026 — 394 subscribers16 August 2026 — 415 subscribers23 August 2026 — 434 subscribers29 August 2026 — 446 subscribers7 September 2026 — 472 subscribers15 September 2026 — 490 subscribers7 August 202615 September 2026
7 measurements spanning 39 days, net +99. 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 376–505 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 01:20490+18
7 Sept 2026, 14:01472+26
29 Aug 2026, 20:28446+12
23 Aug 2026, 15:44434+19
16 Aug 2026, 02:26415+21
7 Aug 2026, 14:06394+3
7 Aug 2026, 07:16391first reading

Engagement

20 posts held, back to 22 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 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤466.7%
👍233.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 6 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 6 reactions 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 22 June 2026 to 5 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

17 Jul 2026, 10:21 UTC642 views1 reactionsread 7 August 2026

🤕远程客服专员 外籍 1000-1200USD 🤕远程风控专员 外籍 1300-1500USD 🤕远程风控组长 外籍 2000-2200USD 🤨🤨🤨🤨🤨🤨🤨🤨 #到岗菲律宾 #基础专员接受小白 #短期远程 #费用报销 🤕初级客服专员 🤕资深客服专员 🤕风控专员 🤕风控组长 🤕运营组长 🤕运营主管 🤨🤨🤨🤨🤨🤨🤨🤨 🇯🇵日本 #大阪 马来西亚 #新山 技术包网 #合法纳税 #法定社保 #合法工程师签证 #有日本签证优先 ✅ GO开发工程师 (日本) ✅ 前端开发工程师 (日本) ✅ 产品经理 ✅资深人事专员(马来居家) 🤨🤨🤨🤨🤨🤨🤨 😜@Nala0067579

❤1

16 Jul 2026, 04:15 UTC514 views0 reactionsread 7 August 2026

😝还有少量名额,有需要的可以随时联系我哦 🤕远程客服专员 外籍 1000-1200USD 🤕远程风控专员 外籍 1300-1500USD 🤕远程风控组长 外籍 2000-2200USD 🤨🤨🤨🤨🤨🤨🤨🤨 #到岗菲律宾 #基础专员接受小白 #短期远程 #费用报销 🤕初级客服专员 🤕资深客服专员 🤕风控专员 🤕风控组长 🤕运营组长 🤕运营主管 🤨🤨🤨🤨🤨🤨🤨🤨 #合法纳税 #法定社保 #合法工程师签证 #外派日本 😳🇲🇾马来西亚技术部火热招募中...😳 ✅ GO开发工程师 😜@Nala0067579

14 Jul 2026, 09:07 UTC436 viewsread 7 August 2026
Photo

远程风控组长 薪资:2000U-2200U 上班地点:远程居家 工作时间:12休2天(轮休) 国籍:外籍 #岗位要求: 1.具备1-2年以上风控团队管理经验 2.熟悉中国综合盘风控审核流程 3.熟悉中国综合盘风控业务逻辑 4.具备风险分析及决策能力 5.具备团队管理及培训能力 #岗位职责: 1.负责风控团队日常管理工作 2.审核重大风险案件及异常会员行为 3.制定及优化风控/出款审核标准 4.协调风控、出款审核等部门工作 5.带领团队完成风控指标目标 —————————————— ⭐️远程待遇福利: ✅ 无休假奖金 500 RMB/月 ✅ 生日津贴 120 USD + 年终红包 + 其他节日礼金 ✅入职满6个月享 10天带薪年假 (如不休假,做满一年,公司给予相应的补贴奖金) ✅工作电脑采购金:2,500(RMB)做满6个月随下月薪资发放 😜@Nala0067579

14 Jul 2026, 09:07 UTC376 viewsread 7 August 2026
Photo

远程风控专员 薪资:1300U-1500U 上班地点:远程居家 工作时间:12休2天(轮休) 国籍:外籍 #岗位要求: 1.具备1年以上BC中国盘风控经验优先 2.熟悉中国体育/彩票综合盘风控知识优先 3.具备风险识别及分析能力 4.逻辑思维清晰,责任心强 5.能够适应轮班制度 #岗位职责: 1.负责平台会员风险审核 2.监控异常投注及风险行为 3.处理风控预警及异常案件 4.协助优化平台风控策略 #岗位要求 1. 有审核风控经验一年优先考虑,无经验者,最好本身玩过球板或信用版,有体育经验,或爱看熟知体育比赛等 2. 反应灵敏,对待问题能独立思考 3. 具备中文读听写的基本能力" ————————————————- ⭐️远程待遇福利: ✅ 无休假奖金 500 RMB/月 ✅ 生日津贴 120 USD + 年终红包 + 其他节日礼金 ✅入职满6个月享 10天带薪年假 (如不休假,做满一年,公司给予相应的补贴奖金) ✅工作电脑…

11 Jul 2026, 14:27 UTC399 viewsread 7 August 2026

各位亲们、远程客服又来了、名额有限、只限#外籍申请哦、薪资待遇很不错! 远程客服 限时8️⃣位 有需要请按照以下格式给我相关资料、以便于尽快帮您安排面试、绝对真实有效、HR直招 #投递格式 1.简历附件 2.打字视频(需要清晰看到本人打字) 2. 小名: 年龄: 性別: 国籍: 目前所在地: 期望职位: 打字数量: 方便面试时间: 🤭😰🤔😱😰😜@Nala0067579

9 Jul 2026, 11:40 UTC433 viewsread 7 August 2026

🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨 #到岗菲律宾 #基础专员接受小白 #短期远程 #费用报销 🤕初级客服专员 🤕资深客服专员 🤕风控专员 🤕风控组长 🤕运营组长 🤕运营主管 🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨 #到岗菲律宾技术岗 #薪资加码 #奖金翻倍 😍AI应用工程师 😍AI / RAG质检 😍AI应用训练与结果评估员 😍Python后端 Coding Maker 😍Playwright自动化采集工程师 🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨 #合法纳税 #法定社保 #合法工程师签证 #外派日本 😳🇲🇾马来西亚技术部火热招募中...😳 ✅ 产品经理 ✅ 运维工程师 ✅ GO开发工程师 ✅ 前端开发工程师 🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨 😩到岗福利一览: 😜无休假奖金 500 RMB/月 😜生日津贴 120 USD+ 其他节日礼金(入职享有)+ 年终奖金 😜 生活补贴70 U/月 😜 入职满6个月享15天带薪年假(若不休假,补贴9000RMB) 😜 机票报销…

9 Jul 2026, 05:22 UTC370 viewsread 7 August 2026

😵到岗菲律宾/职能岗位/可先远程 接受小白,中国籍本科毕业的也接受,专员薪资16000RMB起+绩效 😍运营组长 3000-3500U+绩效 😍客服专员(接受小白)2000U起+绩效 😍资深客服专员 2400-2800U +绩效 😍风控专员 2000-2200U+绩效 😍风控组长 3000-3500U +绩效 😍运营主管 3800-7500U +团队奖金 🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨 😵到岗菲律宾高薪技术岗/可先远程 😍AI应用工程师 5000-8000U +团队奖金 😍AI应用训练与结果评估员/高薪可议价 😍AI / RAG质检 /高薪可议价 😍Playwright自动化采集工程师/高薪可议价 😍Python后端 Coding Maker/高薪可议价 🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨

2 Jul 2026, 10:47 UTC470 views2 reactionsread 7 August 2026

远程客服新增2位、招完即停、不能在大陆、其他无限制、不限国籍

👍2

25 Jun 2026, 11:17 UTC658 viewsread 7 August 2026

😵到岗菲律宾/职能岗位/可先远程 接受小白,中国籍本科毕业的也接受,专员薪资15000RMB起+绩效 😍运营主管 3800-7500U +团队奖金 😍运营组长 3000-3500U+绩效 😍客服专员(接受小白)2000U起+绩效 😍资深客服专员 2400-2800U +绩效 😍风控专员 2000-2200U+绩效 😍风控组长 3000-3500U +绩效 😍HRBP组长 2800-3000U +绩效 🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨 😵到岗菲律宾高薪技术岗/可先远程 😍AI应用工程师 5000-8000U +团队奖金 😍AI应用训练与结果评估员/高薪可议价 😍AI / RAG质检 /高薪可议价 😍Playwright自动化采集工程师/高薪可议价 😍Python后端 Coding Maker/高薪可议价 🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨🤨

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

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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

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

“🛡远程/到岗/菲律宾直招” (@taizihryumi), 490 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/taizihryumi.

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.