Channel
@shuijun2838
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
21subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001881676404 |
|---|---|
| Type | Channel |
| Username | @shuijun2838 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 5 times, most recently 18 September 2026 |
| On Telegram | t.me/shuijun2838 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 19:52 | 21 | -1 |
| 11 Aug 2026, 12:46 | 22 | no change |
| 7 Aug 2026, 14:18 | 22 | first reading |
18 posts held, back to 4 January 2025 — 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 18 posts for this entry, the most recent from 30 July 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.
253 reactions across 1 post, in 6 distinct kinds. The most used accounts for 51.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 129 | 51.0% | |
| 🔥 | 35 | 13.8% | |
| 💯 | 34 | 13.4% | |
| 🐳 | 31 | 12.3% | |
| 👌 | 13 | 5.14% | |
| ❤🔥 | 11 | 4.35% |
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 1 of the 18 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 253 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 4 January 2025 to 30 July 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.
水军 😍😍 推广引流 团队 接单 请看置顶公告 😎😝😝帮客户做效果 🥸😛😍节约资金 控制成本 😉😋🤓真人真量 效果真实 😎😎😋百万团队 合作共赢 😀😀😀😀😀😀😀😀 灰产类目如下： 😃😄😄😄😄😄😄😄😄 😵💫😵💫🤐 😄😄😄😄😄😄😄😄😄 🏳️🌈🏳️🌈🏳️🌈🏳️🌈 😀😀😀😀😀 色播 直播 棋牌 🥸😛😛😛😛 约炮 空降 彩票 🥸🥸🥸😛🥸 综合 体育 数据注水🫰排号🫰发号🫰回执🫰访客点击🫰下载注册🫰平台充值🫰人工假聊+qv/🫰带项目来谈我报价 合作 （嘴炮勿扰） 简介：水军团队全国地区IP真人做任务打造 😍 新用户效果 补新增量 水军 团队接单😀可做市面上一切推广引流类业务只要你有米啥活都干 🫰三网运营商手机卡号码 🫰真人真量接App下载注册充值 🫰一人一机一IP截图交单 🫰线上百万人团队兼职 🫰全网最专业的的IP流量 全国地区不同IP 😀😀 😀😀 支持🥰🥰 🥰 …
定制，无视任何内容飘蓝
你找那水上不好的，找我上 你106扣量雷发不到的找我 你卡发扣量雷发不到的找我 你连上机视频都没有的找我 你连回执记录都没有的找我 希望你能找到我，我能帮到你一点是一点，祝你开工大吉 @shuijunKK
接单：视频+排雷发雷+效果补量+补回执，有需要联系我 ✈️@shuijunKK
补回执记录
水军 团队接单 数据注水效果🫰排雷🫰发雷🫰回执🫰访客点击效果🫰下载注册效果🫰平台充值效果🫰人工假聊效果+qv/🫰 带项目来谈我报价 合作 简介：水军团队全国地区IP真人做任务打造 😍 新用户效果 补新增量 水军 团队接单😀可做市面上一切推广引流类业务只要你有米啥活都干 棋牌，直播，彩票，股票，空降约炮。。。。 🫰移动，联通，电信，真机号码 🫰真人接App下载注册充值效果 🫰一人一机一IP访问点击 🫰大量QQ，VX人工假聊效果操作 🫰全网最专业的的IP流量 全国地区不同IP ✈️@shuijunKK
水军真人团队接单，315已过正常开工，合作发财💰
😀各种行业的下载注册App都可以做 😀各种行业的流量IP全国刷访客点击 量 😀各种行业的粉都可以做假聊天引流话术App下载注册充值 😀各种行业的➕QQ➕Vx活粉死粉 😀😀本团队驰聘沙场十年，主做灰产项目和绿色项目，水军可以帮你挣钱带上你的项目我报价合适就干。
水军补量 pinned «正常开工，水军接单做任务 @shuijunKK»
正常开工，水军接单做任务 @shuijunKK
搞就搞移动，客户吃肉我喝汤，持续接单合作共赢
方式一：假发全假量 方式二：真发大扣量 排雷落地 ，真真假假假假真真 三网数据包🫰找雷🫰发雷🫰人工短信🫰回执
👍129🔥35💯34🐳31👌13❤🔥11
Showing the 12 most recent of 18 posts we hold for @shuijun2838. 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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“水军补量” (@shuijun2838), 21 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/shuijun2838.
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.