求职:三个人在国内长期从事欧洲刷单 求一个业务配套完整的国内工作室从0-1 会打粉 引流杀客全套流程可以独立完成 做火种大黄蜂的脚本以及过人脸的脚本都有 有老板招人的联系一下我 @benleihu101620 ✈️免费投稿:@ahsdbv11

Channel
求职招聘💼
@rmmmm
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
9,993subscribers
-2,572 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002160039976 |
|---|---|
| Type | Channel |
| Usernames | @rmmmm @zhaogongzuo2 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 53 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/rmmmm |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 13:37 | 9,993 | -75 |
| 7 Sept 2026, 04:58 | 10,068 | -130 |
| 5 Sept 2026, 07:22 | 10,198 | -31 |
| 4 Sept 2026, 12:39 | 10,229 | -38 |
| 3 Sept 2026, 13:21 | 10,267 | -34 |
| 2 Sept 2026, 21:36 | 10,301 | -66 |
| 2 Sept 2026, 08:18 | 10,367 | -12 |
| 1 Sept 2026, 18:22 | 10,379 | -14 |
| 1 Sept 2026, 11:18 | 10,393 | -69 |
| 31 Aug 2026, 18:25 | 10,462 | -34 |
| 31 Aug 2026, 11:27 | 10,496 | -70 |
| 30 Aug 2026, 18:34 | 10,566 | -7 |
| 30 Aug 2026, 13:02 | 10,573 | -81 |
| 29 Aug 2026, 16:33 | 10,654 | -9 |
| 29 Aug 2026, 15:48 | 10,663 | -89 |
| 28 Aug 2026, 17:15 | 10,752 | -10 |
| 28 Aug 2026, 13:44 | 10,762 | -63 |
| 27 Aug 2026, 15:29 | 10,825 | -8 |
| 27 Aug 2026, 13:55 | 10,833 | -22 |
| 26 Aug 2026, 17:26 | 10,855 | first reading |
Engagement
286 posts held, back to 6 August 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 40 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 11.4%
- avg views ÷ 9,993 subscribers
- Avg views / post
- 1,140
- 230 posts measured
- Reaction rate
- 0.091%
- reactions ÷ views · ER floor
- Posts in window
- 230
- of 286 held
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 2 of 230 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 286 (6 August 2026 – 29 August 2026) |
| Views total | 262,555 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 12:57 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.
What this channel posts
- Video runtime
- 8m 32s
- Average length
- 12s
Measured directly from 42 videos 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.
Reaction mix
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 3 of the 286 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 286 most recent posts we hold, published 6 August 2026 to 29 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.
Recent posts
求职国内工作室 有7年出海经验,带过团队,做过精聊 群洗 股转币 会FB投流 对工作室的基础搭建技术全懂,擅长群洗,随时可以写剧本甚至大纲 求一个模式成熟的工作室,快杀 远控也可以,低调懂事,人在广东全国可去 @Yes6966 ✈️免费投稿:@ahsdbv11
【2028体育】TG全网最大信誉台 ⚡️⚡️⚡️⚡️⚡⚡⚡⚡⚡ ⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡ ⚡2028体育官网: 20280700.com 大客首选RMB台 不限IP无需实名 限红拉满单笔可出千万 ⚡8K国际官网: 8k3039.com 大客首选U台 U存取大额无忧 返水无上限 限红拉满 福利拉满 TG最大信誉平台 玩家首选人民币台 ⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡ ⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡ ⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡ ⚡ 笔笔存款送 1% U存U提不限提款次数 ⚡ 全网福利天花板/首复存送/投注送 众多活动全开 ⚡ 月投注送嫩模空降/劳力士赠送/神秘彩金每天狂撒500万 ⚡ 平台支持 USDT 微信 支付宝 K豆等100多种钱包 2028体育全站会员封神榜: ⚡ 某神秘大哥麻将胡了爆奖1100万 ⚡ 世界杯大哥精准命中狂澜590万 ⚡ 大佬PG电子麻将胡了拿下472万 【#2028体育丨全网福利天花板】 新客户首存50…
人在国内 诚心想出去做事 有没有公司在招人 证件齐全 随时都可以出发 不是墨迹的人 联系方式 @llss111122 ✈️免费投稿:@ahsdbv11
你好,可以帮我发一个帖子嘛,国内男,找项目,底子干净,低调做事,干业务好手,来个好老板,长期做 @hsss456 ✈️免费投稿:@ahsdbv11
【N1国际】U投首选平台|全球第一 |值得信赖 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️N1国际官网: n10944.com 大客首选U台 U存取大额无忧 返水无上限 限红拉满 福利拉满 ⚡️2028体育官网: 20280700.com 大客首选RMB台 不限IP无需实名 限红拉满单笔可出千万 ⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡ ⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡ ⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡ ⚡️N1超神时刻: 😫百家乐神秘大佬出手精准预测成功提款925万U 😫PG电子麻将胡了2 爆爆爆 喜提870万U 😫PP糖果电子大哥6u进场59047U离场以小博大 ⚡️N1国际正统场馆: 😘#Choice真人视讯限红20万u一口 😘#DB真人视讯限红50万U一口 😘#PG电子限红3000U一啦 😘#PP电子限红800U一啦 😘#支持任意平台vip等级平移 ⚡️N1国际官网: n10944.com ⚡️2028体育官网: 2…
想找个稳定事情做,国内工作室国外都行,有过精聊方面的经验,✈️ @songbei98 ✈️免费投稿:@ahsdbv11
找个工作,最好是快杀性质的。国内工作室国外都行,最好有底薪,出国要管票,骗子勿扰联系 @qifei096 ✈️免费投稿:@ahsdbv11
【182体育】TG全网最大信誉台|千万无忧 东南亚顶级线上娱乐 🤪🤪🤪🤪 182体育官网: 1821468.com 大客首选RMB台 不限IP无需实名 限红拉满单笔可出千万 Y3国际官网: y30526.com 大客首选U台 U存取大额无忧 返水无上限 限红拉满 福利拉满 😀😀😀😀😀😀😀😀😀😀😀😀😀 ⚡⚡⚡⚡⚡⚡⚡⚡⚡⚡ 大户首选(安全保障客户信息安全) 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 😜幸运加持:《极速糖果1000》单笔爆出 559万 😜天选之子:《麻将胡了》连胡不断 提款684万 😜赏金王者:《赏金女王》凭借运气狂揽 343万 😅😚😏😝😍😀😃😃😅😏🙃😢 🔤🔤🔤🔤 以及C币,K豆,OKpay、👌微信,👌支付宝,银行卡等30多种存取款方式,通畅便捷 😍😁😁😁😁☺️🔥❤️😁😁🔥😁🔥☺️🔥 加入 #182体育 赶紧来领取 电子可拉2万一注 182体育官网: 1821468.com Y3国际官网: y…
求职:三个人在国内长期从事欧洲刷单 求一个业务配套完整的国内工作室从0-1 会打粉 引流杀客全套流程可以独立完成 做火种大黄蜂的脚本以及过人脸的脚本都有 有老板招人的联系一下我 @benleihu101620 ✈️免费投稿:@ahsdbv11
诚心求职,目前负债压力大,迫切想要踏实工作挣钱还债。 做过精聊、国内快杀,沟通能力强,上手快,愿意学习服从安排,只想好好做事。 谢绝各类中介,收割套路类岗位就不必联系了,我不是小白,不想白费时间。 有真实靠谱岗位的老板欢迎对接 @xj88911 ✈️免费投稿:@ahsdbv11
🫤😐🫥😶🤥🫠🤫🫡🫢 😑 N9 国际认证 | 信誉平台 支持5倍验资 【验资:@N9KF】 担保域名:N9.TOP 点击查看 ⚡️⚡️⚡️⚡️ 💝 新会员好礼 注册就送28.8U 新人首存/二存/三存最高赠送8️⃣8️⃣8️⃣8️⃣U 💝 老会员好礼 电子狂欢每日存款赠送10% 充值笔笔送3%无上限 夜间充值最高可优惠8888U ⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 香港六合彩 4️⃣8️⃣.8️⃣ 倍 加拿大28全网返水最高 ⚡️注册网址:N9.PRO 😇🧐🧐😗🧐😙😄 ⚡️ 官方客服: @N9KF ⚡️ 官方飞投: @N9N9 ⚡️ 彩票客服: @N9CP ⚡️ 彩票飞投: @N9N9N9 ⚡️ 福利频道: @N9pd888 ⚡️ 注册网址: N9.COM【USDT】 ⚡️ 注册网址: N9.C…
Showing the 12 most recent of 286 posts we hold for @rmmmm. 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 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.
Names
Channels on the register whose handles appear in this channel's posts.
@jbgj · 13,63722 posts🏆九博国际@JBGJ🏆上下分群 总押900万美金
@jiubovip · 8,80422 postsN9.COM|官方频道
@N9_com1 · 11,65021 postsN9.COM 福利频道导航
@n9pd888 · 7,96121 posts【2028126.com】赌王之王
@pgdzr · 7,49615 postsU99贵宾会-官方频道
@U99GBH · 3,50613 posts8T娱乐城 官方-频道
@www8tcom · 42,57811 postsN1娱乐城-赌王之王
@N1YLC8 · 6,3068 posts2028122.COM- 2028体育官方频道
@pg115 · 13,3817 posts182体育官方频道
@ty182gf · 5,9316 posts182体育官方频道
@VIP182PP · 5,2306 posts超级引擎🔍 @CJYQ
@cjyq · 929,6282 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.
Appears in Telegram’s recommendations for other channels
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.
@rjjjj · 42,534
Telegram ranks this channel #2 of 55 here — alongside 54 others — read 27 August 2026
@xii34 · 100,161
Telegram ranks this channel #46 of 69 here — alongside 68 others — read 15 August 2026
@qzzpfabu888 · 623,380
Telegram ranks this channel #50 of 72 here — alongside 71 others — read 9 August 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“求职招聘💼” (@rmmmm), 9,993 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/rmmmm.
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.