Channel
@xlzp1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,093subscribers
-20 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002930145405 |
|---|---|
| Type | Channel |
| Username | @xlzp1 |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/xlzp1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 18:59 | 1,093 | -4 |
| 29 Aug 2026, 04:33 | 1,097 | -1 |
| 26 Aug 2026, 06:04 | 1,098 | -3 |
| 23 Aug 2026, 04:05 | 1,101 | -2 |
| 20 Aug 2026, 02:47 | 1,103 | -1 |
| 16 Aug 2026, 17:37 | 1,104 | -6 |
| 12 Aug 2026, 21:08 | 1,110 | -3 |
| 9 Aug 2026, 20:38 | 1,113 | no change |
| 9 Aug 2026, 14:48 | 1,113 | first reading |
9 posts held, back to 12 January 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 9 posts for this entry, the most recent from 2 March 2026. 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.
18 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5404521343293073282 | 6 | 33.3% | |
| custom 5343939171725617118 | 5 | 27.8% | |
| custom 5197630131534836123 | 4 | 22.2% | |
| custom 5461151367559141950 | 3 | 16.7% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 3 of the 9 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 12 January 2026 to 2 March 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.
行业正在洗牌。 强公司在留下，弱公司在逃。 还在带人去兰卡的， 本质只有一个原因 —— 在柬埔寨活不下去。 跟着强公司：稳定发展 跟着弱公司：全球流浪 别把跑路包装成机会。 也别拿未来陪别人试错。 选择一次，少走三年弯路。 📩 联系方式 👉 直接私聊：@lailai997 🤖 双向联系：@lailai995BOT
custom 53439391717256171181custom 54045213432930732821custom 54611513675591419501
招聘启事 🌟 薪资福利 💰 月薪：30K - 50K 🎉 满年奖：满一年奖金 30000 元 🗓 14个月薪资（1年14薪） 🏖 带薪休假：每半年可休假 17 天 💎 分红福利：入职满3个月,每个月可享分红 1万 - 10万,随工资发放 分红根据公司盈利发放 每个岗位有固定分红比例 🚀 招聘岗位 ✅ 前端开发工程师 前端招聘jd 1、5 年前端开发经验以上 2、有 SaaS 系统开发经验，熟悉租户隔离、权限管理、国际化（i18n）及动态配置方案 3、精通 Vue 3 / React 及 TypeScript，具备大型项目重构与复杂状态管理经验 4、精通CSS 预处理器（Sass/Less），对CSS 变量和组件库定制化 5、熟练使用 Vite/Webpack 等构建工具，具备插件开发和打包配置调优能力 6、具备AI Agent写代码能力 📩 联系方式 👉 直接私聊：@lailai997 🤖 双向联系：@lailai99
custom 51976301315348361232custom 53439391717256171182custom 54611513675591419502
有单身的需要找工作的吗📍 哈哈哈
custom 54045213432930732825custom 51976301315348361232custom 53439391717256171182
招聘 1个 高级运维， 3个 前端开发，月入50K 运维工程师招聘jd 一、岗位职责 1.负责服务器（Linux 为主）的部署、运维与日常管理 2.保障业务系统 稳定性、高可用性、安全性 3.负责应用发布、版本回滚、故障排查与应急处理 4.搭建和维护 监控、告警、日志系统 5.编写运维脚本，实现自动化运维 6.配合开发完成 CI/CD、容器化、云资源管理 7.参与系统架构优化、性能调优与容量规划 二、任职要求 1.熟悉 Linux 系统（如 Ubuntu、CentOS），具备扎实的系统管理经验。 2.熟悉网络基础（TCP/IP、HTTP、DNS 等），具备较强的故障排查能力。 3.熟悉常见 Web 与中间件部署，如 Nginx、Tomcat、Redis、MySQL 等。 4.熟悉 Shell、Python 或 Go 等脚本语言，具备自动化运维经验。 5.熟悉 CI/CD 工具，如 Jenkins、GitLab CI 等。 6.具…
🍽 公司年夜饭现场实拍 澳龙上桌，海鲜满席，各种美食安排到位。 不分职位，不分岗位，所有在职员工同等待遇。 在这里，大家不仅是同事，更像一家人。 让每一位在外奋斗的人，都能感受到家的温度。 ——— 📍 我们长期招聘中 ✔️ 包吃住 ✔️ 福利稳定 ✔️ 团队氛围好 ✔️ 真实公司环境 想找工作 / 想换环境 / 想稳定发展 欢迎咨询了解 📩 联系方式 👉 直接私聊：@lailai997 🤖 双向联系：@lailai995BOT
公司影院+健身房 公司宿舍+夫妻房 公司食堂+日常饭菜 公司环境+楼上俯拍 📩 联系方式 👉 直接私聊：@lailai997 🤖 双向联系：@lailai995BOT 📂点击：查看岗位合集
UI 岗位职责 1.负责公司 Web / H5 / App / 后台系统 的 UI 设计工作 2.根据产品需求输出 高保真 UI 设计稿（Figma / Sketch 等） 3.参与产品前期讨论，能从 用户体验 & 视觉角度 提出设计建议 4.维护设计规范（色彩、组件、字体、间距等），保证设计一致性 5.与产品经理、前端开发紧密配合，推动设计方案落地 6.跟进开发还原度，参与 UI 走查和优化 UI任职要求 1.3 年以上 UI 设计经验，有完整项目案例 2.熟练使用 Figma（必备），熟悉 Sketch / PS / AI 等工具 3.具备良好的 视觉设计能力：布局、配色、字体、组件感 4.理解 Web / H5 / App 设计规范（iOS / Android 基础规范） 5.能独立完成从需求理解 → 设计输出 → 设计交付 6.沟通顺畅，有责任感，能和产品、研发高效协作 薪资范围 30K – 45K （根据面试表现与…
✅ 前端工程师 2名 💰 薪资：30K–50K（按能力定） +每个月岗位独立分红 岗位职责： 1、负责公司相关业务前端开发 3、负责公司产品的PC客户端前端开发工作； 4、与产品、设计、后端紧密配合，按时高质量完成开发任务，沉淀相关文档 岗位要求： 3年以上前端领域开发经验； 深入掌握 HTML/CSS/JavaScript等前端技术，有一定JS原生能力； 熟悉Web前端组件化/模块化开发模式和前端工程化实践；至少精通一种前端开发框架，如React、Vue、Angular等;具有强烈的学习欲望，自驱意识；具有良好的沟通能力、团队协作能力；具有较强的逻辑思维能力、抗压能力；具备良好的问题分析与解决能力； 优秀的代码组织、界面布局、编码风格干净、利落； 有良好的产品意识和团队合作意识，能够和产品、UI交互部门协作完成产品面向用户端的呈现 踏实稳定，不挑活，不排斥简单重复的工作。 加分项: 有Electron、Node、Flutte…
🔥【高薪直招｜软件测试】🔥 工作职责 1.熟悉软件测试理论和流程，掌握常见测试方法（功能 / 回归 / 冒烟等） 2.熟悉 Web 项目测试，了解常见的前端、后端交互逻辑 3.至少熟悉一种接口测试工具（Postman、Apifox、JMeter 等） 4.能独立编写清晰、可维护的测试用例和缺陷报告 5.具备良好的沟通能力和责任心，有质量意识 6.掌握 SQL，能进行基本的数据校验 💰 薪资：30K–50K（根据面试能力定薪） ⏰ 工作时间：8小时 / 月休4天 🎁 福利待遇：🍱 包三餐 + 宵夜 🎁 14 薪 + 37天年终奖+生日礼物+节日福利 📩 联系方式 👉 直接私聊：@lailai997 🤖 双向联系：@lailai995BOT 📂点击：查看岗位合集
Showing the 9 most recent of 9 posts we hold for @xlzp1. 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 — 407,981 of 1,629,571 entries 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.
Named by 3 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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“柬埔寨-找工作-公司直招” (@xlzp1), 1,093 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/xlzp1.
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.