Channel
@Tpithr88888
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,332subscribers
+86 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002071976754 |
|---|---|
| Type | Channel |
| Username | @Tpithr88888 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/Tpithr88888 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 04:13 | 2,332 | +40 |
| 25 Aug 2026, 22:33 | 2,292 | +10 |
| 23 Aug 2026, 03:53 | 2,282 | +15 |
| 20 Aug 2026, 02:03 | 2,267 | +7 |
| 17 Aug 2026, 11:14 | 2,260 | +9 |
| 10 Aug 2026, 20:44 | 2,251 | +4 |
| 8 Aug 2026, 01:06 | 2,247 | +1 |
| 7 Aug 2026, 18:48 | 2,246 | no change |
| 7 Aug 2026, 18:26 | 2,246 | first reading |
20 posts held, back to 31 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 pageof Telegram’s post history, 20 posts per page.
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 4 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (31 July 2026 – 7 August 2026) |
| Views total | 7,574 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 18:48 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.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.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 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 2reactions 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 31 July 2026 to 7 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.
8/7 #迪拜 #行政 岗位：行政人事 工作地点：迪拜 国籍：外籍 非中国籍 语言：中文英文 工作内容： 1. 负责办公室日常行政事务、物资采购、资产管理 2. 协助员工入职、住宿、签证/证件资料整理 3. 对接宿舍、办公区、供应商及本地外勤事务 4. 协助安排会议、接待、文件归档 5. 完成主管交办的其他行政支持工作 任职要求： 1. 有行政、人事助理、前台、文员相关经验优先 2. 熟悉基础办公软件，做事细心、有责任心 3. 沟通协调能力好，抗压，执行力强 4. 形象气质佳，稳定性高 5. 能接受迪拜当地工作安排 薪资：试用期 2200U，转正 2500U（依能力面议） 到岗：迪拜 求职联系 @tphrcindy121212
8/7 #第三国远程 #産品总监 包网产品总监 项目：巴西市场及其他海外包网 ⭕️项目经验必须 岗位职责 1. 负责公司游戏平台（包网、电子、真人、体育、棋牌等）的整体产品规划、路线图及版本管理，对产品结果负责。 2. 管理产品需求及优先级，负责需求评审，确保产品逻辑、用户体验及开发效率。 3. 管理产品、UI、UX团队，建立产品流程、PRD及需求评审规范。 4. 协调开发、测试、UI等团队，推动项目按计划上线并保障交付质量。 5. 持续分析市场、竞品及用户需求，优化活动、VIP、推广、游戏大厅、留存及充值转化体系。 6. 建立数据驱动的产品优化机制，关注DAU、留存率、充值率、ARPU/ARPPU、活动ROI及用户转化等核心指标。 7.持续优化用户体验、操作流程及产品商业化能力。 任职要求 1. 5年以上互联网产品经验，3年以上产品团队管理经验。 2. 有完整产品负责人经验，能够独立负责产品规划、路线图、版本及项目落地。 …
8/6 #远程 #UI 远程UI 薪资范围：15k-20k 工作时间：试用期9小时月休4 #岗位要求： 1. 男女不限， 21-35岁，大专及以上学历； 2.工艺美术相关专业毕业，具有良好的美术基础和审美能力； 3.熟练使用Photoshop、Flash、IIIustator等常用设计制作软件工具,，了解Dreamwear和Div+css等，有设计经历者优先； 4.积极肯干，吃苦耐劳；具有创新精神及团队协作精神；责任心强，还有良好的沟通能力； 工作职责： 1. 负责公司的站内外广告、图片、动画、海报、logo及网页的设计制作； 2．认真做好公司各类图片信息和主题资料的收集、整理、归档工作； 3．协助网站编辑、网站优化推广专员进行网站专题和网站美化工作； 4．完成公司、部门领导交办的其他事务； 备注：需会做动效，有棋牌，游戏相关经验 面试需要提供作品集 求职联系 @tphrcindy121212
8/6 #到岗 #马来 #産品经理 综合盘産品经理 项目：综合包网(棋牌，电子，体育等) 新大楼上班 薪资大约3万5~5万+ 马来签证，大小周，包吃住 要求：28岁以下，3年项目经验 @kirakira1214
8/6 #出入款 #外籍 #菲律宾 💖 急招5名-出入款 宿舍办公 🥰【岗位描述】： 1.看出单，给会员上下分以及处理存取款问题 2.在线解答客户的咨询疑问，并及时推介公司最新活动 3.掌握客户需求，快速妥善处理客户各种问题 🍭1个月 9k元 🍭2个月 9k元 🍭3个月 9k元 🍭4个月 10k元 + 3k绩效 🍭5个月 10,5k元 + 3k绩效 🍭6个月 11k元 + 3k绩效 🍭7个月 11,5元 + 3k绩效 🍭8个月 12k元 + 3k绩效 🍭9个月 12,5k元 + 3k绩效 🍭10个月 13k元 + 3k 绩效 🍭11个月 13,5k元 + 3k绩效 🍭12个月 14k元 +…
8/5 #先远程后到岗 可外籍也可接受中国籍 地点 :菲律宾索莱尔 客服组长 运营组长 风控组长 求职联系 @tphrcindy121212
8/5 #远程 #UI 远程UI 薪资范围：15k-20k 工作时间：试用期9小时月休4 #岗位要求： 1. 男女不限， 21-35岁，大专及以上学历； 2.工艺美术相关专业毕业，具有良好的美术基础和审美能力； 3.熟练使用Photoshop、Flash、IIIustator等常用设计制作软件工具,，了解Dreamwear和Div+css等，有设计经历者优先； 4.积极肯干，吃苦耐劳；具有创新精神及团队协作精神；责任心强，还有良好的沟通能力； 工作职责： 1. 负责公司的站内外广告、图片、动画、海报、logo及网页的设计制作； 2．认真做好公司各类图片信息和主题资料的收集、整理、归档工作； 3．协助网站编辑、网站优化推广专员进行网站专题和网站美化工作； 4．完成公司、部门领导交办的其他事务； 备注：需会做动效，有棋牌，游戏相关经验 面试需要提供作品集 求职联系 @tphrcindy121212
8/4 #Go #日本 📢 招聘｜资深 Golang 后端工程师（Web3方向） 地点： 日本大阪 薪资： 6000-9000U 台湾、马来西亚籍优先，中国也可以 📍工作内容 ‧ 负责高并发后端服务及 API 开发 ‧ Web3 / EVM 链相关开发（RPC、WebSocket、链上数据处理等） ‧ 微服务架构、数据库与缓存优化 ‧ Docker、Kubernetes 容器化部署 📍任职要求 ‧ 3 年以上 Golang 开发经验 ‧ 熟悉 MySQL、PostgreSQL、Redis ‧ 熟悉 Kafka、RocketMQ、Pulsar 等至少一种消息队列 ‧ 熟悉 Gin、Fiber、Kratos 等 Go 框架 ‧ 熟悉 Docker、Kubernetes 📍加分项 ‧ Web3 / 区块链 / EVM 项目经验 ‧ WASM（Go / Rust）开发经验 ‧ 熟悉 Prometheus、Grafana、Jaege…
8/4 #日本 2026年8月招聘岗位： 日本🇯🇵技术岗位： 1、Rust工程师👨💻 2、Cocos前端工程师🧑💼 3、高级产品经理👨💻 4、高级测试工程师👩💻 5、运维工程师👨💻 日本🇯🇵其他岗位： 1、客服专员（台湾或马来西亚籍） 2、数据分析师（非中国籍） 3、产品调研专员（非中国籍） 4、人事主管（非中国籍） 其他非日本岗位： 1、视讯厅运营经理🧑💼 薪资：30～40k，非中国籍，中英文流利 2、现场值班客服 薪资：15～19k，非中国籍，中英文流利 基本要求：所有日本岗位🧮需具有全日制统招本科学历。 签证：日本岗位统一办理日本技术人文签证，公司缴纳雇佣保险+劳灾保险+社会健康保险+厚生年金 求职联系 @tphrcindy121212
8/4 #菲 #居家 #golang 岗位名称：golang工程师 工作时间：10小时，月休4 工作地点：菲律宾居家 薪资待遇：30~40K + 房补 + 餐补 + 项目奖金 工作内容：负责公司大型站群系统的开发和管理 相关经验：有CMS系统开发经验者优先 岗位职责 1. 负责公司CMS（内容管理系统）、门户网站矩阵及SaaS化内容服务平台的核心模块设计与Go语言后端开发。 2. 推进CMS系统的改造与高并发架构优化，满足千万级PV、高并发访问及海量数据存储的稳定性需求。 3. 能够设计灵活的内容模型（如自定义字段、多语言支持、分类体系）、权限管理（RBAC）及工作流引擎。 4. 设计并实现CMS插件化机制、模板引擎解析及API开放平台（如OpenAPI等），方便第三方系统集成与二次开发。 5. 对接各大CDN加速服务、对象存储（OSS）、搜索引擎（Elasticsearch）及第三方营销组件。 6. 编写高质量代码及技…
8/3 #Go #远程 #只要台湾人 只要台灣人，在台灣遠程 職位：資深後端工程師 / 技術型全端工程師，偏支付系統 主要協助內容： 1. 維護與擴充支付平台後端服務 協助設計商戶接口、後台接口、callback、worker 的責任邊界 2. 串接第三方支付通道，處理簽名、回調、查單、補單、對帳 3. 維護 MySQL / Redis / RabbitMQ 相關交易流程 4. 協助部署、排查 log、處理交易異常與系統穩定性問題 必要能力： 1. 熟 Go，能看懂並維護 go-zero、gin 2. 熟 MySQL schema 設計、交易資料一致性、migration 3. 熟 Redis 冪等、鎖、快取 4. 熟 RabbitMQ、MQ retry、dead-letter、非同步補償 5. 懂支付訂單狀態機：代收、代付、callback、補單、對帳、重試 5. 能設計 API 邊界，不會把後台接口和商戶接口的責任混…
8/3 #安卓 #远程 #只要台湾人 只要台灣人，在台灣遠程 📢 誠徵：Android 高階技術工程師（全遠端／專職） 工作型態：全遠端 · 專職 ━━━━━━━━━━━━━━━━━━ ▎工作內容 1. Android 系統底層技術研究：系統修改、ROM 客製化、Root 權限管理 2. 銀行與金融類 App 環境偵測繞過機制研究：root 偵測、模擬器偵測、安全性檢測等機制破解 3. 短信（SMS）相關腳本開發與破解：自動化攔截、解析、模擬發送等技術實作 4. 刷機與系統調校：熟悉 Magisk、KernelSU、LSPosed、Xposed 等框架運用 5. 安全性測試與逆向工程：Android 應用反編譯、Hook、動態分析 ━━━━━━━━━━━━━━━━━━ ▎我們希望你具備的條件 ✅ 精通 Android 系統架構，熟悉 AOSP 編譯與修改 ✅ 熟練使用 Magisk / KernelSU / …
❤1
Showing the 12 most recent of 20 posts we hold for @Tpithr88888. 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 — 312,896 of 1,626,935entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“树人国际人力资源 官方频道 求职招聘” (@Tpithr88888), 2,332 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/Tpithr88888.
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.