Channel
@zhaopinHRlulu
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
4,118subscribers
-4,803 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001534608700 |
|---|---|
| Type | Channel |
| Username | @zhaopinHRlulu |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/zhaopinHRlulu |
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 13 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 |
|---|---|---|
| 19 Sept 2026, 03:16 | 4,118 | -243 |
| 14 Sept 2026, 19:38 | 4,361 | -650 |
| 11 Sept 2026, 16:01 | 5,011 | -298 |
| 7 Sept 2026, 10:19 | 5,309 | -426 |
| 3 Sept 2026, 00:05 | 5,735 | -476 |
| 30 Aug 2026, 18:18 | 6,211 | -656 |
| 27 Aug 2026, 18:24 | 6,867 | -127 |
| 24 Aug 2026, 18:07 | 6,994 | -22 |
| 20 Aug 2026, 21:32 | 7,016 | -2,992 |
| 19 Aug 2026, 19:53 | 10,008 | -15 |
| 18 Aug 2026, 20:34 | 10,023 | -252 |
| 17 Aug 2026, 17:37 | 10,275 | -203 |
| 16 Aug 2026, 15:22 | 10,478 | +2,544 |
| 12 Aug 2026, 23:25 | 7,934 | -494 |
| 10 Aug 2026, 09:50 | 8,428 | -420 |
| 7 Aug 2026, 16:50 | 8,848 | -73 |
| 7 Aug 2026, 11:30 | 8,921 | no change |
| 7 Aug 2026, 11:27 | 8,921 | first reading |
8 posts held, back to 1 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 19 pages 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 8 posts for this entry, the most recent from 7 August 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.
14 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 71.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 71.4% | |
| 👍 | 3 | 21.4% | |
| 🔥 | 1 | 7.14% |
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 8 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 1 June 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.
监察专员/组长/主管 4名 GJ：外籍 NL：21-35岁 XL：大专及以上 XZDY：10k-25k区间 入职泰国 GWXQ： 1. 具备三年以上的监察岗位经验，有充分的查舞弊的经验及技能。 3. 对中文理解无障碍，逻辑思维有组织，语言表达清晰，抗压能力强。 4. 取证经验丰富，面谈技巧丰富。 5. 有过全流程舞弊调查经验的优先，接受返聘，但需要特批的都不考虑。 6. 具有保密意识。 GWZZ： 1.通过财务数据，分析与查找舞弊线索，并进一步排查与锁定舞弊事项。 2.通过各飞机群组核查舞弊举报线索，并进一步查证事项的真实性与责任人。 3.接受举报投诉进行查证，梳理举报反映问题线索，形成专项报告。
❤1
马尼拉招聘职能岗位： 24H综合专线客服专员 （不要中国籍） 后勤片区专员 外籍（不要中国籍） 档案管理专员 国籍不限 风控质检专员（斯里兰卡） 联系人事：@ovolulu
柬埔寨天推转化部门，我3个人选在里面干了半年以上，未被优化。 稳定资源部门，直播转化扶持，待遇10转12k。 点位面试聊，专员都能进去稳定20k以上。 优先返聘/懂体育跟国内的小白。 联系人事：@ovolulu
❤4
迪拜要维护专员，不接受返聘。 底薪1万r 夜班补贴2500r 餐补2700r 绩效能拿到就是1万 2万 3万起步 一个月综合2w左右 转正办理白产长期签证 去slk泰国过渡（中国籍）开始上人。最好是中国籍哦。 维护底薪10000，如果转去slk，底薪是13000～ 福利待遇等咨询人事～ 在职人事：@ovolulu 黑名单也可以～ ============ 🖤集团直招 🤩入职找lulu 🧸吃喝玩乐 🍪生活分享
更新下岗位： 小白岗位：▪️质检专员（泰国/菲律宾） ▪️稽查专员（迪拜） ▪️行政专员（迪拜） 入职泰国：▪️电竞监测专员 （TH） ▪️体育监测专员 （TH） ▪️体育/电竞业务组长 （TH） ▪️运营专员（棋牌） （泰国） ▪️大客专员（泰国） 入职菲律宾：▪️采购专员 10K-14K 福利待遇等咨询人事～ 在职人事：@ovolulu ============ 🖤集团直招 🤩入职找lulu 🧸吃喝玩乐 🍪生活分享
❤2👍1
7月岗位更新。。。。 福利待遇等咨询人事～ 在职人事：@ovolulu ============ 🖤集团直招 🤩入职找lulu 🧸吃喝玩乐 🍪生活分享
❤2🔥1
更新下岗位： 小白岗位：▪️公关专员（DB） ▪️敏感信息专员（PH） 入职泰国：▪️电竞监测专员 （TH） ▪️体育监测专员 （TH） ▪️体育/电竞业务组长 （TH） ▪️运营专员（负责棋牌） （TH） 更新中。。。。。 🔴稳定在职3年人事 入职找我 用心负责 🔴@ovolulu（公司直招人事） 🔴迪拜要客服，中国/缅甸/越南/印尼/马来/泰国籍可直飞 ============ 🖤集团直招 🤩入职找lulu 🧸吃喝玩乐 🍪生活分享
现在泰国曼谷要客服了，如果需要的话可以安排入职泰国曼谷哦。只要有经验的。 底薪10000起步，9休4，有餐补105r/天。 其他福利待遇来问我。 在泰国的小伙伴抓紧问我～ 🔴稳定在职3年人事 入职找我 用心负责 🔴@ovolulu（公司直招人事） 🔴迪拜要客服，中国/缅甸/越南/印尼/马来/泰国籍可直飞 🔴赛事开始了，需求会减少了哦～
👍2❤1
Showing the 8 most recent of 8 posts we hold for @zhaopinHRlulu. 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.
@zhaopinHRlulu edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Named by 9 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“泰国 迪拜 斯里兰卡 土耳其/客服维护/招聘直招 HR-露露” (@zhaopinHRlulu), 4,118 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/zhaopinHRlulu.
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.