Telegram RegisterThe public register of Telegram
Telegram profile photo for 水手鱼台

Channel

水手鱼台

@shuishouyutai

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

757subscribers

+146 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003434578754
TypeChannel
Username@shuishouyutai
CreatedBetween 1 November 2025 and 3 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live2 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/shuishouyutai

Topic

Hacking & security — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 the other topics.

Growth

6117576847 August 2026 — 611 subscribers7 August 2026 — 613 subscribers8 August 2026 — 613 subscribers15 August 2026 — 625 subscribers21 August 2026 — 632 subscribers28 August 2026 — 646 subscribers4 September 2026 — 656 subscribers12 September 2026 — 679 subscribers25 September 2026 — 694 subscribers5 October 2026 — 706 subscribers13 October 2026 — 713 subscribers20 October 2026 — 741 subscribers26 October 2026 — 747 subscribers2 November 2026 — 757 subscribers7 August 20262 November 2026
14 measurements spanning 87 days, net +146. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 589–779 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Nov 2026, 15:19757+10
26 Oct 2026, 22:56747+6
20 Oct 2026, 21:46741+28
13 Oct 2026, 23:55713+7
5 Oct 2026, 17:57706+12
25 Sept 2026, 03:57694+15
12 Sept 2026, 15:56679+23
4 Sept 2026, 22:21656+10
28 Aug 2026, 20:54646+14
21 Aug 2026, 14:37632+7
15 Aug 2026, 08:12625+12
8 Aug 2026, 03:03613no change
7 Aug 2026, 21:37613+2
7 Aug 2026, 18:34611first reading

Engagement

16 posts held, back to 3 January 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 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 16 posts for this entry, the most recent from 16 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 43s
Average length
2m 43s

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.

Reaction mix

7 reactions across 4 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7100.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 8 of the 16 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 3 January 2026 to 16 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.

Recent posts

16 Jul 2026, 12:35 UTC626 views2 reactionsread 8 August 2026
Photo

❤️水手电商鱼台强势来袭|年中重磅福利重磅上线 短信源码 900 + 套 全面适配 3dapi、wp、shopyy、shopify 多类电商平台 同行越来越多竞争加剧,直放底价回馈各位合作老板 原价:月卡199,季卡488,年卡1288,永久卡1588 ⏰限时福利周期:7.16–7.31 ✅月卡囤货特惠:买 2 赠 1,多囤多省 ✅年卡永久调价:仅需 888u ✅永久卡永久调价:仅需1088u ✅老客户专属权益:持有未到期月卡,补差价即可升级年卡 我们的服务: ❤️免费定制短信源码 ❤️两班倒客服轮值,平均消息响应<1 分钟 ❤️后台持续迭代更新,合理后台需求均可开发落地 购买联系:@ssyutai

❤2

7 Jul 2026, 14:06 UTC729 views3 reactionsread 8 August 2026
Photo

支持钓CK了,现阶段还只支持简单的劫持账户密码+ck(简单需求能满足的可以联系定制),功能还在完善中。 后续想法,比如进入某个官网,他所有功能都是和官网相同的,但是当使用信用卡支付的时候,把账单信息劫持到后台。(制作周期可能会很久,需要一边做一边补充功能,有想法的老板可以提前联系,那种小众的可以搞到流量,然后官网有正常的支付逻辑的,就能够用这种方法) 电商支持wp,shopify,shopyy了 有需要的老板联系 @ssyutai

❤3

24 May 2026, 06:21 UTC≈1,300 views0 reactionsread 8 August 2026
Photo

自定义验证码功能已进行新版升级,目前支持更多、更完整的页面设计能力,可实现更加复杂、灵活的自定义页面效果。 新版功能支持复制 AI 提示词,并结合 AI 设计能力进行页面生成与调整,尽可能做到“所见即所得”。相比旧版本,新版不再受原有规则限制,整体自由度更高,适合有更高自定义需求的用户使用。 当前新版功能仍处于测试阶段,暂时仅支持部分国家和地区使用。美国、英国、日本等部分国家暂不支持。测试无误后,将会支持所有源码。 同时,旧版本自定义功能后续仅支持导入使用,不再支持编辑。如需体验新版功能,可根据自身需求选择更新。由于新版仍在测试中,更新后可能存在部分兼容性或使用问题,请按需操作。 如果出现更新后发现问题请联系 @ssyutai

13 May 2026, 07:59 UTC≈1,200 views0 reactionsread 8 August 2026

📢 后台已更新 700+ 套源码,覆盖大部分欧洲、美洲、非洲国家 ✨ 支持各国官网免费定制,如果没有现成源码,也可免费定制。 ✨ 包括但不限制于包裹、交通罚单、积分 ✨ 效率说明:一般第二天完成,任务多时会排班处理。 需要的老板联系 @ssyutai

15 Apr 2026, 07:37 UTC≈1,710 viewsread 8 August 2026

后台激活到期了,出现问题都要更新一下,使用安装命令更新

24 Mar 2026, 20:20 UTC≈2,190 views0 reactionsread 8 August 2026
Photo

上次修复之后,还是存在被登录读取数据区的情况,排查日志之后基本排除漏洞。需要二次更新,设备登录之后,当前账户被强制绑定在这个浏览器,无法在其他位置登录。如果需要别处登录,需要管理员在用户管理处解绑。解绑之后需要在30秒钟之内登录,否则会被二次上锁。更新需要使用安装命令更新,然后需要测试前端是否能够正常打开,打不开的,需要更新源码。

23 Mar 2026, 05:46 UTC≈1,950 viewsread 8 August 2026

防洪优化 1.优化美国交通罚款在3.18号更新之后容易红的问题 2.重新构建所有前端源码(在3.23号更新之后,在之前版本下载的前端将不可用,需要把所有下载过的源码全部更新一遍,存在问题可以联系我),后续的新增源码不支持旧版本,兼容旧版本的过渡将在4.1号全部移除。 3.新增防洪D,对比防洪A拦截范围更小,避免防洪A开起来之后上鱼效果比不开好的情况,欢迎各位老板对比参考 4.新增后台源码防洪刷新功能。

20 Mar 2026, 12:31 UTC≈1,770 viewsread 8 August 2026
Photo

台子发现重大漏洞,可能会导致被登录偷鱼,大部分发生在早上11点左右,请检查之后,更新服务器(要重新安装,清空掉所有之前的数据,包括域名和鱼),通过简单域名 + 简单入口就有可能被攻击,如:https://flhsmv.gov-xxx.bond/dmv。请务必更新掉服务器在发鱼。

19 Mar 2026, 03:20 UTC≈1,540 viewsread 8 August 2026

美国防洪A在新版本出现问题了,跑美国的老板昨天更新了的,今天二次更新一下,然后没有更新的老板,不需要新功能的就不用更新了。

18 Mar 2026, 05:13 UTC≈1,460 views1 reactionsread 8 August 2026

近期更新 1.ID分流功能(设置里面开启) 我们新增了ID分流机制,用户可以自定义可见ID尾号,从而实现更灵活的流量分流管理。此功能使每个用户都能拥有个性化的ID分配,显著提升系统的流量处理能力。 2.自动拒绝标记为绑的账户(设置里面开启) 为简化操作并提升安全性,系统现已支持自动拒绝标记为“绑”的账户,彻底解放双手,避免人工审核的繁琐,从而提高工作效率。 3.后台域名状态检测 新增后台域名状态自动检测功能,用户可以在仪表盘实时查看域名状态。 4.防洪A开启提醒 针对跑美国的用户,建议开启防洪A功能,以避免域名过快被标记为红。此举有助于提升域名的稳定性和健康性。

❤1

8 Mar 2026, 09:02 UTC≈1,510 viewsread 8 August 2026

近期更新 1.域名去重功能 我们现已支持域名的去重功能。如果同一用户在不同域名下多次下单,系统会自动判断并只计算一次订单。去重规则基于 IP地址、邮箱、手机号码、卡号 来进行匹配。 2.游客与工作号域名可见性设置 现在,游客和工作号可以根据需求设置域名的可见性,方便管理哪些域名对外展示,提升操作的灵活性。 3.自定义验证码模板重做 自定义验证码模板功能已重新设计,并新增实时预览功能,您可以在设置时查看验证码的最终效果,操作更直观、便捷。 4.新增美国交通罚款数据 近期更新了近百套新的美国交通罚款数据,老板们可以尝试使用, 5.技术号更换通知 原技术号掉线,我们已更换为新的技术号:@ssytjishu 。有需要的朋友可以通过新号联系。

11 Feb 2026, 16:00 UTC≈1,810 viewsread 8 August 2026

农历二十六至正月初八期间,因技术人员放假,暂不接收定制业务。 期间台子如出现问题,正常售后不受影响。 目前已补齐美国大多数州的交通罚款服务。 值此新春之际, 祝各位老板 马年行大运,生意长虹,订单不断,回款顺利,财路稳健,事事顺心。 新的一年,合作共赢,共创佳绩,年年有鱼 🧧🐎

Showing the 12 most recent of 16 posts we hold for @shuishouyutai. 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.

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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“水手鱼台” (@shuishouyutai), 757 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/shuishouyutai.

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.