Channel
@zhaopinchanhr
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
328subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001781140482 |
|---|---|
| Type | Channel |
| Username | @zhaopinchanhr |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/zhaopinchanhr |
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 22 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 12:16 | 328 | -2 |
| 8 Sept 2026, 14:56 | 330 | -6 |
| 30 Aug 2026, 14:04 | 336 | +6 |
| 23 Aug 2026, 23:25 | 330 | -2 |
| 16 Aug 2026, 18:35 | 332 | +7 |
| 8 Aug 2026, 09:00 | 325 | +1 |
| 8 Aug 2026, 07:20 | 324 | no change |
| 7 Aug 2026, 13:38 | 324 | first reading |
20 posts held, back to 22 November 2024 — 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 22 February 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
12 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 58.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 58.3% | |
| 🎉 | 5 | 41.7% |
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 9 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 12 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 November 2024 to 22 February 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
#岗位：资深 Golang + PHP 开发工程师 工作地点在泰国芭提雅 也可以考虑在菲律宾全职远程办公 #上班时间：从中午12点到21点，月休6 我们需要你： 同时精通 Golang 和 PHP，并具备丰富的实战经验 对高并发、分布式系统有深入理解，能够设计高性能、高可用的架构 具备良好的代码设计能力和工程化思维，注重代码质量和性能优化 热爱技术，具备独立解决问题的能力，并愿意探索新技术 具备良好的沟通能力和团队协作精神 你的职责： 负责公司核心业务系统的设计、开发和维护，包括需求分析、架构设计、编码实现、测试和部署 参与技术方案选型和架构设计，持续优化系统性能、稳定性和可扩展性 编写高质量、可维护的代码，并进行代码审查，确保代码规范和技术标准的落地 与产品经理、设计师和其他开发人员紧密合作，确保项目按时高质量交付 关注 Golang 和 PHP 生态发展，积极学习和探索新技术，并分享给团队成员 技…
🎉3❤2
#岗位：Flutter 开发工程师 工作地点在泰国芭提雅 也可以考虑在国内全职远程或在菲律宾远程办公 上班时间：从中午12点到21点，月休6 我们正在寻找一位经验丰富的 Flutter 开发工程师，加入我们充满激情和创造力的团队！ 如果你： 对 Flutter 充满热情，并拥有丰富的跨平台应用开发经验 具备扎实的 Dart 语言基础，并能熟练运用 Flutter 框架和常用库 拥有良好的代码风格和编程习惯，注重代码质量和性能优化 具备独立解决问题的能力，并能积极学习和探索新技术 拥有良好的沟通能力和团队合作精神 那么，你就是我们要找的人！ 你的职责： 负责公司移动端产品的 Flutter 应用开发，包括需求分析、架构设计、编码实现、测试和部署 参与技术方案选型和架构设计，持续优化应用性能和用户体验 编写高质量、可维护的代码，并进行代码审查 与产品经理、设计师和其他开发人员紧密合作，确保项目按时高质…
❤2🎉1
#招聘岗位：电销专员 需求人数： 1 #待遇：固定班12.00 - 22.00 10休4 入职：10000 转正：12000 #基本要求： -女性 -可以接受入住公司提供的宿舍，居家办公 -接受小白 岗位职责：打电话回访会员，做好会员回归事宜
❤1🎉1
#急招岗位：金流副组长（2位） #待遇：8休2，1720u-2000u+绩效 #要求：有运营经验，优先当过金流组长
#急招：2名 #岗位：推广维护 #要求：不限国籍，需有女有经验，能理解中文 #待遇：12小时休2 ， 12K 转 15K+提成
#岗位：包网客服 需求人数： 3 #待遇： 9休4 入职：10k 转正：12k #基本要求: ⁃ 不限国籍 ⁃ 不限性别 ⁃ 最好有包网客服的经验，一般在线客服也可 ⁃ 护照签证状态需要正常，护照必须在手 ⁃ 能长期待在菲 #岗位职责： ⁃ 平时负责对接包网客服事宜
#岗位：包网商务 需求人数： 1 #待遇： 10 休4 入职：10k 转正：12k #基本要求: ⁃ 不限国籍 ⁃ 不限性别 ⁃ 最好有包网商务的经验，但不是硬性要求 ⁃ 护照签证状态需要正常，护照必须在手 ⁃ 能长期待在菲 #岗位职责： ⁃ 平时负责对接包网商务事宜
#岗位：项目助理（1名） #待遇： 10 休4 入职：10k 转正：12k #基本要求: ⁃ 不限国籍 ⁃ 不限性别 ⁃ 有推广经验 ⁃ 护照签证状态需要正常 ⁃ 能长期待在菲 #岗位职责： ⁃ 平时负责收集市场信息和执行主管交代的一些事物
#岗位：市场推广 - 在菲居家 #需求人数： 1-3人 #待遇： 12休2 入职：12000CNY 转正：15000CNY+提成 #基本要求；对体育知识有一定的了解 #岗位职责：负责开发维护新老用户。
#岗位：质检：1名 #待遇： （8休2，在菲居家办公，转正后才享有餐房补） 入职：715+715=1430u 转正：860+860=1720u #基本要求 1、有综合盘客服组长、客服质检员经验，擅长表格制作，有长期工作打算优先 2、人在菲，护照在手上 【人选上手合格后需要立即提交护照，人事约定地点收取护照并核对是否本人】 3、无任何不良记录，无赔付，情绪稳定，有独立思考和分析问题的能力 4、自带设备 #岗位职责： 1.按部门要求检查平台每日所有客服线是否达到回线标准 2.负责汇总每日的客服线数据，并登记客服当日的接线情况 3.根据平台情况优化并制定新话术 4.指导客服回线，提升客服线质量 5.敢于提出并改善旧制及不合理方案
#祝大家新年快乐🥰 #happynewyear2025
MAKATI 老牌集团-Chan HR人事直招 pinned «🔥Makati 集团 - 在招岗位： 1. #财务记账 9休4， 1720 $-2150 $ +绩效，要求 女有经验 2. #电维 10休4，1430 $-1720 $+绩效，无夜班，要求 女中文好 3. #客服副组长 9休4， 2000 $+绩效，要求 有客服组长经验，会英文优先 4. #风控/稽核 8休2，1500…»
Showing the 12 most recent of 20 posts we hold for @zhaopinchanhr. 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.
Named by 2 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“MAKATI 老牌集团-Chan HR人事直招” (@zhaopinchanhr), 328 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/zhaopinchanhr.
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.