三角洲❤️公益算法解密内核 🎮真正的算法解密,不动任何内存,绝对安全的程序 📲APP启动器不依赖mt管理器,完美规避终端检测 ✅物资显示,过滤高价值物资,精确寻包 🐱人物骨骼,射线,头甲显示 完全公益免费,卡密随便输入即可 全网真正的三角洲公益算法解密,不收取任何费用,无任何套路 ✨更新时间:2026年11月23日 🎮栖月 Kernel公益运营团队 栖月频道: https://t.me/yuenhpdd
👍118
Signed xixi Ieuan

Channel
@BIGFATFISH6
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
42,081subscribers
+41,442 since we began measuring on 28 September 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1004436351264 |
|---|---|
| Type | Channel |
| Username | @BIGFATFISH6 |
| Description | 交流群 https://t.me/dfy998 交流群记得过验证 封号找这个机器人 @yx_codexbot 有事联系本人 @dfy6236 我不会主动私信你们索要钱财切勿上当受骗 大肥鱼完全工艺如有收费则是骗子 本频道所有文件皆由ChatGPT制作,仅供个人学习研究;使用者的任何行为与应用作者无关,请在下载后24小时内删除,下载即代表同意本协议,若有侵权违法行为请联系我删除内容 |
| Created | Between 1 June 2026 and 28 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 September 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/BIGFATFISH6 |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @BIGFATFISH6/1299 · this entry2 Nov 2026, 01:32 UTC | @HeiXuePD/340663 Nov 2026, 08:04 UTC | 1.00 | 31 hours |
| @HeiXuePD/3469510 Nov 2026, 01:52 UTC | @BIGFATFISH6/1846 · this entry10 Nov 2026, 10:06 UTC | 1.00 | 8.2 hours |
| @HeiXuePD/3475210 Nov 2026, 13:53 UTC | @BIGFATFISH6/1865 · this entry10 Nov 2026, 13:53 UTC | 1.00 | under a minute |
| @BIGFATFISH6/1930 · this entry11 Nov 2026, 02:08 UTC | @HeiXuePD/3478511 Nov 2026, 02:08 UTC | 1.00 | under a minute |
| @BIGFATFISH6/1281 · this entry1 Nov 2026, 13:52 UTC | @LinYuKernel/776842 Nov 2026, 03:46 UTC | 1.00 | 14 hours |
| @LinYuKernel/774241 Nov 2026, 00:57 UTC | @BIGFATFISH6/1299 · this entry2 Nov 2026, 01:32 UTC | 1.00 | 25 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @HeiXuePD | 9 (8/8 hand-verifiable sample passed) | 1.00 | 8.0 hours | @HeiXuePD (6–3) |
| @LinYuKernel | 7 (7/7 hand-verifiable sample passed) | 1.00 | 11 hours | @LinYuKernel (4–3) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 5 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 92 comparable posts for this entry, running 28 October 2026 to 13 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Recorded under the keys clone_copy · clone_mutual, last confirmed 13 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 19:19 | 42,081 | +7,670 |
| 10 Nov 2026, 15:11 | 34,411 | +2,228 |
| 9 Nov 2026, 02:17 | 32,183 | +1,340 |
| 7 Nov 2026, 18:47 | 30,843 | +1,373 |
| 6 Nov 2026, 14:25 | 29,470 | +1,258 |
| 5 Nov 2026, 15:16 | 28,212 | +1,351 |
| 4 Nov 2026, 15:15 | 26,861 | +596 |
| 3 Nov 2026, 14:36 | 26,265 | +583 |
| 2 Nov 2026, 11:07 | 25,682 | +506 |
| 1 Nov 2026, 11:47 | 25,176 | +536 |
| 31 Oct 2026, 15:20 | 24,640 | +365 |
| 30 Oct 2026, 16:46 | 24,275 | +347 |
| 29 Oct 2026, 16:10 | 23,928 | +380 |
| 28 Oct 2026, 15:37 | 23,548 | +333 |
| 27 Oct 2026, 18:40 | 23,215 | +444 |
| 26 Oct 2026, 20:17 | 22,771 | +566 |
| 25 Oct 2026, 18:19 | 22,205 | +975 |
| 24 Oct 2026, 15:41 | 21,230 | +809 |
| 23 Oct 2026, 14:54 | 20,421 | +227 |
| 22 Oct 2026, 17:11 | 20,194 | first reading |
422 posts held, back to 28 September 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 31 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 422 (28 September 2026 – 13 November 2026) |
| Views total | 1,065,952 |
| Reactions total | 41,530 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 14:18 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.
Lifetime counters from Telegram’s own channel header, read 13 November 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.
Measured directly from 14 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.
41,542 reactions across 422 posts, in 47 distinct kinds. The most used accounts for 92.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 38,369 | 92.4% | |
| ❤ | 1,148 | 2.76% | |
| 👏 | 490 | 1.18% | |
| 🥰 | 279 | 0.672% | |
| 🤔 | 169 | 0.407% | |
| 😁 | 130 | 0.313% | |
| 😡 | 125 | 0.301% | |
| 🐳 | 103 | 0.248% | |
| 🖕 | 81 | 0.195% | |
| 😘 | 80 | 0.193% | |
| 🔥 | 67 | 0.161% | |
| 👎 | 66 | 0.159% | |
| 😍 | 61 | 0.147% | |
| 🤣 | 59 | 0.142% | |
| custom 6039414971039750530 | 46 | 0.111% | |
| 😭 | 43 | 0.104% | |
| custom 6086888812225499750 | 28 | 0.067% | |
| 🍌 | 26 | 0.063% | |
| custom 6041895035480318807 | 22 | 0.053% | |
| 💯 | 22 | 0.053% | |
| 27 further kinds | 128 | 0.308% |
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 422 of the 422 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 41,542 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 422 most recent posts we hold, published 28 September 2026 to 13 November 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.
Telegram’s own ‘edited’ marker: 14 of 421 posts held from the last 30 days (3.33%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
三角洲❤️公益算法解密内核 🎮真正的算法解密,不动任何内存,绝对安全的程序 📲APP启动器不依赖mt管理器,完美规避终端检测 ✅物资显示,过滤高价值物资,精确寻包 🐱人物骨骼,射线,头甲显示 完全公益免费,卡密随便输入即可 全网真正的三角洲公益算法解密,不收取任何费用,无任何套路 ✨更新时间:2026年11月23日 🎮栖月 Kernel公益运营团队 栖月频道: https://t.me/yuenhpdd
👍118
Signed xixi Ieuan
🎮 大肥鱼三角洲网盘下载链接 🎮 🎉你们每天点一点转存下载嘻嘻🎉 📥📥📥📥📥📥📥📥📥📥📥📥📥 https://pan.quark.cn/s/6061a5d18530 公益卡密联系机器人每日获取 @bbblajibot 🤩新手小白详细使用辅助教程点我查看
👍194
Signed TGBot Pro
此频道已经被官方盯上了.即将停止使用.点击下面蓝色字体进入新频道更新⬇️⬇️ 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道 此频道即将停用.点击此蓝色字体加入新的频道
👍200
Signed 阿呆 (全网收管理) @adggku
🥰三角洲0.1元数据号 【📸 红狼数据号 三角洲账号】 🟠全网唯一一家包冻结的 🟠 全网质量最好,服务最好的 🟠纯人工验号,保障账号100%质量 ✅直登号/数据号下单卡网:https://shop.a9fkw.cn/shop/888 ❤️1-12级(0-10M):0.1元❤️ ❤️12-29级(0-100M):3元❤️ ❤️30-60级(0-100M):6元❤️ ❤️12-18 级直登号【包冻结】3元❤️ ❤️30-60 级直登号【包冻结】6元❤️ 👑为什么选择我们? 😀 假一赔十: 描述不符?我们承诺十倍补偿! 😀秒速售后:.交易或登录遇任何问题,客服实时响应。 😀 源头把控: 只出精品,垃圾号在我们这里根本过不了审。 ✅ 承诺:不卖垃圾号,卖垃圾号死一家 ✅直登号/数据号下单卡网:https://shop.a9fkw.cn/shop/888 ❤️售后客服:@hsnbsjh
👍223
三角洲双子星公益解密更新算法解密 正在公益中!欢迎体验!解决3.0迷雾 🔥11.13最新更新双子星2.1 更新内容如下: 1.更新适配最新算法解密 2.优化卡顿 3.适配最新par驱动 🔗公益频道 🔥驱动1 🔥驱动2 🔥双子星公益解密卡密获取/疑难杂症问题 🌟🙃🌟➡️ @SZXNBPD ❗️❗️➡️ @SZXPD777 合作客服联系 @szxnb888
👍206custom 60394149710397505308custom 60416560033704253781custom 60418950354803188071
Signed 故事
🔥HERO免费开盒助手🔥 🌈开盒专用🌈 🌈HERO户籍猎手 安装包下载链接 https://wwaqk.lanzoub.com/i7JQI4epmicb 密码:8888 🔨支持免费查询:手机号、身份证、QQ号、微信号、抖音号、银行卡、车牌号、邮箱、贴吧ID、微博ID、钉钉、快手、闲鱼号、小红书、网易云ID、脸书、推特、名下财产、开房记录、IMEI。涵括多元档案信息。支持模糊身份证、手机号补齐,支持全国猎魔/更多功能看软件详情... 🥰官方卡密售卖机器人⬇️⬇️ 👉 @ATC_AutoShop_Bot 👈 注: 最老猎手之一 也是唯一猎手其余仿冒 唯一权威官方频道 t.me/PLCOINP/8
👍190custom 60394149710397505303
Signed 全网买管理@ai520i
不听话的人推荐拉去枪毙
👍193custom 604189503548031880713
Signed 大肥鱼
前天我不是都说了飞天不能用了吗,为什么还有人头铁去下载使用呢?然后拉闸了跑了骂我?
👍177custom 60394149710397505302😍1
Signed 大肥鱼
太稳了 连打不加密来了😘
👍165custom 60394149710397505302
Signed 大肥鱼
纯c也稳
👍178custom 60394149710397505302🐳1
Signed 大肥鱼
Photo, posted without a caption
👍176custom 60416560033704253782
Signed 大肥鱼
有不懂不会的一律看这里都懂了都会了
👍175custom 60868888122254997508custom 60394149710397505306custom 60532029928809458172
Signed 大肥鱼
Showing the 12 most recent of 422 posts we hold for @BIGFATFISH6. 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.
We recorded 8 posts on @BIGFATFISH6 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 53 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“BIG FAT FISH 公益频道(大肥鱼)” (@BIGFATFISH6), 42,081 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/BIGFATFISH6.
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.