Channel name was changed to «米乐集团招聘频道»
Channel
米乐集团招聘频道
@xituofenbu
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
6subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001525792157 |
|---|---|
| Type | Channel |
| Username | @xituofenbu |
| Description | 米乐集团广招人才,给予伙伴们发挥的舞台! 官方认证HR:@fazai2022888 不禁足 可以外宿房补15000P 13薪 +年终奖 过节礼金 生日礼金 等等福利 赔付透明, 宿舍1-2人间,有保姆打扫房间,冰箱,微波炉,电磁炉,厨房,wifi应有尽有,欢迎马来西亚,印尼,越南,中国,台湾,等等的国家前来求职! |
| Created | 29 April 2022 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/xituofenbu |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 05:15 | 6 | no change |
| 13 Aug 2026, 05:05 | 6 | first reading |
Engagement
6 posts held, back to 29 April 2022 — 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 6 posts for this entry, the most recent from 29 April 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 3
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
底薪12000-14000 房补15000P 餐补12000P 水电补助200RMB 9休6
底薪12000-14000 房补15000P 水电补助200RMB 10休4 提成3-10%
底薪12000-14000 房补15000P 水电补助200RMB 9休4 提成3-10% 电维绩效ABC等级 2000-6000
File, posted without a caption
Channel created
Showing the 6 most recent of 6 posts we hold for @xituofenbu. 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“米乐集团招聘频道” (@xituofenbu), 6 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/xituofenbu.
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.