Channel
@shuiyizuanshishou
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,153subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001826085335 |
|---|---|
| Type | Channel |
| Username | @shuiyizuanshishou |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/shuiyizuanshishou |
Crypto & trading — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 |
|---|---|---|
| 25 Sept 2026, 17:36 | 3,153 | +3 |
| 16 Sept 2026, 23:57 | 3,150 | -6 |
| 13 Sept 2026, 02:58 | 3,156 | +4 |
| 9 Sept 2026, 02:14 | 3,152 | -6 |
| 3 Sept 2026, 22:18 | 3,158 | +1 |
| 31 Aug 2026, 09:54 | 3,157 | -5 |
| 27 Aug 2026, 23:26 | 3,162 | +6 |
| 20 Aug 2026, 15:03 | 3,156 | +7 |
| 17 Aug 2026, 19:07 | 3,149 | +3 |
| 14 Aug 2026, 18:48 | 3,146 | +1 |
| 11 Aug 2026, 09:43 | 3,145 | -4 |
| 8 Aug 2026, 10:12 | 3,149 | -4 |
| 7 Aug 2026, 11:17 | 3,153 | first reading |
19 posts held, back to 20 April 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 3 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 19 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
25 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 68.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 68.0% | |
| 👍 | 4 | 16.0% | |
| 🔥 | 4 | 16.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 13 of the 19 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 20 April 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.
奶酪平台即将发射的250X战绩宝贝鳗鱼（BabyManyu）新项目🧀🐸奶酪青蛙（CHEESE HEAD ）（由PePe设计师独家设计）敬请关注！ 预售额度：40B （电报、推特、QQ、地推工作室共计对接400+社区） 发射市值：3-4万美金区间（全流通） 0x696B057564C6b5251A1fD9b90FBf20C454E96666 🧀预售链接：https://www.cheesepad.ai/sale/bsc/0x081b543827E46Dc784524f4D3fFa150Dc2cb71bd 🟣 预售时间：8月9日 12:00 UTC（中国时间8月9日晚上8点整） 🟣发射时间：8月9日晚暂定 🟣http://cheesehead.vip 🟣https://x.com/cheeseheadbsc 🟣https://t.me/Cheeseheadbsc 🇨🇳 https://t.me/Cheeseheadc
现金猫台子的第一个币 0x4f0d7ea112547af5dad59959d98b6a8ee3355bcc
现金猫dev买了 $LEVCAT，自己去验证一下 位置可能有点高 自己找位置 自己看着来 0x02c2faedb05cc1ddd40738a975f57d217ad33ecc
👍2
$ANON 0x93c5d5f12bcdc0fb7a3539547306d4b58b6da19f 有点像下一个epug
👍1
🤑目前蝴蝶币股底池的一些标的 在这里稍微做了一个总结 🤑SPCXB 龙头 0xfe189e97832da1573e4e4ff034f4ffc3a15c7777 MARSCOIN（已上排行榜及阿尔法） 0x79d9e7a73fdb95751e1a0d013e121d3be4517777 SpaxeXcoin （CZ dev也买了） 🤑SKHYB 0x0d2591f26a43a3ce0a40f1fe8609b03962527777 RAM 🤑SPYB 0x08a3eea0f5a2d2db26bb83590cc3961f0a4f7777 SP69 🤑XAUT 0x25953078ab08b6738be8a572c2a123d019627777 黄金时代 🤑QQQB 感觉还不错的 0x8641dbc05a2eee6634c9060198f3efec19487777 BinanceShares 0x6528a3220ecd1…
15❌
❤3
10❌
🔥3
7❌
❤2👍1🔥1
3❌
❤3
黄仁勋刚开通了推特账号 @JensenHuang ，英伟达附属账号，标志性皮夹克 0x5ef897526d488c220de6038fefcc7f5f2492aba3
❤1
Robinhood chain使用教程 友情提示：在Robinhood Chain买币一定要注意池子！！！ 在uniswap用钱包买的话，假如是 virtuals_io的币，一般需要 $VIRTUAL去买，除非项目方加了E交易对。Uni的提醒不到位，不少人买小池子波动太大了亏钱。 用bot买的话，Debot和BasedBot 都可以用e直接买，支持中文，自带跨链 1、跨链工具 BasedBot https://t.me/based_eth_bot?start=r_1697362314 Relay https://relay.link/bridge/robinhood portal https://portal.arbitrum.io/bridge?destinationChain=robinhood-chain&sanitized=true&sourceChain=ethereum 2、RPC（钱包自动添加网…
❤2
https://x.com/KKSCTO/status/2068321090292867512?s=20
Showing the 12 most recent of 19 posts we hold for @shuiyizuanshishou. 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.
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.
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 5 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Water｜Gambles🎲Calls💦” (@shuiyizuanshishou), 3,153 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/shuiyizuanshishou.
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.