梁山泊🏆🈵赔扫雷公群876 :https://t.me/+dZNwEHORFP03NGYx 梁山泊🏆🈵赔扫雷公群6789 :https://t.me/+DvmESKBqJ4E2Yzdk ✅🈵赔扫雷 1-99 🈵赔 ✅限红8000 不上头 想输都难 ✅ 发送【返水】即可领取返水 🤝 不为赚钱,只为交朋友 四海之内皆兄弟,八方豪杰聚梁山!共谋前程,同护忠义,广招天下贤才,共谋前程
👍1
Signed 水泊梁山🈵扫雷

Channel
@diaosile99
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
30,776subscribers
+299 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002694792376 |
|---|---|
| Type | Channel |
| Username | @diaosile99 |
| Description | 没有什么简介,只有发红包 |
| Created | Between 1 April 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/diaosile99 |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
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 word for word on 1 other registered channel. 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 |
|---|---|---|---|
| @diaosile99/18638 · this entry7 Aug 2026, 12:54 UTC | @DFHSTYLT/181067 Aug 2026, 12:54 UTC | 1.00 | under a minute |
| @diaosile99/18640 · this entry7 Aug 2026, 13:21 UTC | @DFHSTYLT/181087 Aug 2026, 13:21 UTC | 1.00 | under a minute |
| @diaosile99/18642 · this entry7 Aug 2026, 13:42 UTC | @DFHSTYLT/181107 Aug 2026, 13:42 UTC | 1.00 | under a minute |
| @diaosile99/18644 · this entry7 Aug 2026, 15:01 UTC | @DFHSTYLT/181117 Aug 2026, 15:01 UTC | 1.00 | under a minute |
| @diaosile99/18674 · this entry7 Aug 2026, 16:44 UTC | @DFHSTYLT/181157 Aug 2026, 16:44 UTC | 1.00 | under a minute |
| @DFHSTYLT/180886 Aug 2026, 16:51 UTC | @diaosile99/18685 · this entry7 Aug 2026, 18:34 UTC | 1.00 | 26 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @DFHSTYLT | 15 (8/8 hand-verifiable sample passed) | 0.99 | under a minute | @DFHSTYLT (15–0) |
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. 15 of the 15 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 15 comparable posts for this entry, running 7 August 2026 to 7 August 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.
Across the whole group of 2, the earliest publisher we hold is @DFHSTYLT. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 7 August 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 00:36 | 30,776 | -9 |
| 13 Aug 2026, 13:07 | 30,785 | +39 |
| 12 Aug 2026, 13:06 | 30,746 | +33 |
| 11 Aug 2026, 10:37 | 30,713 | +41 |
| 10 Aug 2026, 14:02 | 30,672 | +103 |
| 9 Aug 2026, 13:12 | 30,569 | +70 |
| 8 Aug 2026, 13:47 | 30,499 | +11 |
| 7 Aug 2026, 15:36 | 30,488 | +11 |
| 7 Aug 2026, 10:01 | 30,477 | first reading |
383 posts held, back to 7 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 22 pagesof 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. It is computed over the 30 of 383 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 August 2026 |
|---|---|
| Posts held | 383 (7 August 2026 – 15 August 2026) |
| Views total | 77,114 |
| Reactions total | 27 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 14:39 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 15 August 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.
27 reactions across 26 posts, in 3 distinct kinds. The most used accounts for 55.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 55.6% | |
| 👍 | 11 | 40.7% | |
| 👏 | 1 | 3.70% |
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 30 of the 383 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 27reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 383 most recent posts we hold, published 7 August 2026 to 15 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.
梁山泊🏆🈵赔扫雷公群876 :https://t.me/+dZNwEHORFP03NGYx 梁山泊🏆🈵赔扫雷公群6789 :https://t.me/+DvmESKBqJ4E2Yzdk ✅🈵赔扫雷 1-99 🈵赔 ✅限红8000 不上头 想输都难 ✅ 发送【返水】即可领取返水 🤝 不为赚钱,只为交朋友 四海之内皆兄弟,八方豪杰聚梁山!共谋前程,同护忠义,广招天下贤才,共谋前程
👍1
Signed 水泊梁山🈵扫雷
澳博集团|🈵赔硬碰硬 顶级体验 · 尊享待遇 😀公群每日红包😛😚😚😚 U 😀VIP 红包群每日 😜😚😚U 澳博全网最敢送红包的集团 😃福利来系列 😁澳博集团公群: 😃公群708· 澳博加拿大🈵赔2.84 押金109999u【特殊红包奖励最高288u】【每日专属红包】【每日公群388U+1888U红包】【VIP福利群】 😃公群211·澳博🈵赔1:1扫雷 押金69999u【特殊红包奖励最高288u】【VIP福利群】 😃公群006 · 澳博集团扫雷 🈵赔1:1押金29999U【特殊红包奖励最高288u】【VIP福利群】 😃公群117· 澳博加拿大🈵赔2.17 押金19999u【特殊红包奖励最高288u】【每日专属红包】【每日公群388U+1888U红包】【VIP福利群】
👍1
Signed 群管@FLL0
😀⚡️😀⚡️⚡️赔率拉满 实力对碰 随时赢 随时提!不赌不知时运到 只有赌博有来回; 😀😀⚡️😀😀⚡️😀😀⚡️⚡️ 👍 公群红包奖励 : 豹子:奖励 ⚡️⚡️⚡️ 最大:奖励 ⚡️⚡️ 最小: 奖励 ⚡️⚡️ 尾数8: 奖励 ⚡️ 👍红包链接:https://t.me/c/2696906924/4425577 🔯全飞机高胜率台子,没有之一!实力硬碰硬! 1️⃣🔤 VIP晋级奖励⚡️⚡️⚡️⚡️ 2️⃣🔤公群红包奖励⚡️⚡️⚡️ 3️⃣🔤福利群每日红包⚡️⚡️⚡️ ‼️‼️具体活动详情以公群置顶为准! =============================== 😃😀😃😀 304公群 🇨🇦高博PC2.84 满赔 305公群 🇨🇦高博PC2.0 满赔 308公群 🎲高博满赔扫雷🈵 ⚡⚡⚡⚡⚡😀⚡⚡⚡⚡⚡ 👍今日财富密码:大双2000u,2000×6.79=13580 大双13580u,1…
Signed 群管@FLL0
全网首家🈵赔pc 反水群来了 本群客户给1%亏损 千1流流水 群里直接打反水即可 亏损晚上12点后发放 7.25日起累计5000流水私信客服进入 vip群 每日188u红包 昨日流水🈵500u以上 红包金额x2倍 昨日流水🈵1000u以上 红包金额x5倍 昨日流水🈵5000u以上 红包金额x8倍 昨日流水🈵10000u以上 红包金额x18倍 领取翻倍的私信 @shun0596 金额和倍数 私聊后请耐心等待 不私信的默认无流水 包括每日公群红包😀😀😀😀 https://t.me/c/2573321290/5929412 ----------------------------------------- 👍 公群红包奖励 : 豹子:奖励 ⚡️⚡️⚡️ 最大:奖励 ⚡️⚡️ 最小: 奖励 ⚡️⚡️ 尾数8: 奖励 ⚡️ ⚠️温馨提示: 👍豹子奖励不含0,为纯豹子 👍最大最小奖励公群红包更新后第一位和最后一位视为最大…
Signed 群管@FLL0
😀公群137 • 远洋集团 • 满赔扫雷 ————————————————— ☀️游戏赔率: • 下注:1-5000:满赔1:1 • 下注:5001-10000:实时反水0.5% ✔️ 限红:1-10000 ✔️ 佣金:5000以上(抽佣5%) ✔️ 纯流水实时返水,无任何亏损模式! ✔️ 发送【返水】即可领取! ————————————————— 😀远洋大食堂福利群 💲 夜宵福利1️⃣8️⃣8️⃣➖2️⃣8️⃣8️⃣ 💲 抢到正顺/豹子/137:奖励28 💲 截止0点以截图为准 💲 当日流水1000即可领取 💲 流水达5000即可进福利群 💲 公群红包每日9️⃣9️⃣9️⃣18包 ————————————————— 😀远洋集团 • 满赔扫雷💥 公群137 · 远洋集团 · 满赔扫雷 🧧每日红包9️⃣9️⃣9️⃣18包🧧 https://t.me/c/28838568…
Signed 群管@FLL0
🔥 【公群137 · 押金13777U 远洋扫雷硬碰硬】正在派发 红包! 🧧 金额:999 USDT 🎁 数量:18 个 ⏳ 还剩:18 个 ⚡ 手快有,手慢无! 👥 仅限群成员领取
Signed 福利来钱包 @FLLQB
🤣🤣🤣🤣🤣🤣🤣🤣 😃福利来 X 锦鸿国际总上押500万⚡️❤️ 😀😀😀😀😀😀😀😀😀😀😀😀😀😀 开业大酬宾:拿福利砸客户,打造全网第一家满赔带福利公群集团 1️⃣每日客户VIP红包群⚡️⚡️⚡️⚡️⚡️ 2️⃣无论盈亏每日各公群置顶⚡️⚡️⚡️⚡️—⚡️⚡️⚡️⚡️⚡️⚡️ 3️⃣无论盈亏流水翻倍最高⚡️⚡️⚡️倍⚡️ 4️⃣亏损奖励最高⚡️⚡️⚡️倍⚡️ 5️⃣无论盈亏红包幸运数字奖励最高⚡️⚡️⚡️⚡️⚡️ 🤣🤣🤣🤣🤣🤣 🔍旗下公群:👤 ❤️公群0001·押金139999U 锦泓国际满赔扫雷·多重福利 (满赔2.0不抽水)(每日VIP客户红包群)(流水红包翻倍最高118倍)(亏损红包翻倍最高118倍)(特殊红包奖励) ❤️公群0002·押金68888U 锦泓国际高赔高反扫雷 (单注5000以下不抽水)(单注5001以上实时反水2.3%)(每日群红包置顶888U)(每日VIP客户红包群)(流水红包翻倍最高118倍)(…
Signed 群管@FLL0
来金财 · 好运来💵 🥰全部采用TG官方骰子开奖· 公平公正 🥰资金雄厚· 等你来挑战!体验顶级游戏环境· 超级VIP待遇· 尽在金财! 扫雷专区· 实力对决!掷出属于你的好运一刻!😀 😃公群686· 扫雷高反水 上押19999u 🧧:点击领取 😃 公群777· 🈵倍扫雷· 上押11777u 🎲全网最硬快三群· 豹子赔付· 不抽水 😃 公群307· 手摇快三 上押10307U 😃 公群4444· 阿达西手摇快三 上押44444U 😃 公群875· 阿达西快三 上押10000U 🈵赔· 加拿大2.8🇨🇦 😃 公群1314· PC2.84 满倍 上押98888U 🧧:红包点击领取 / 双倍惊喜 金财集团·高德系列 😘 金财集团·🈵倍扫雷 硬碰硬 😘 金财集团·加拿大PC2.0🈵倍 😘 金财集团·加拿大PC2.8🈵倍 金财集团· 德州扑克 😃 公群458· 金财德州竞技 上押20000U 🎰 V…
Signed 群管@FLL0
🟢🟢🟢🟢🟢🟢🟢🟢🟢 🟢🟢🟢🟢🟢 🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢 稳盈综合游戏:@wyyl 👈一键开启 🀄🟢🟢🟢🟢🟢 ① 充值大赠送 ⑥ 电子幸运注单 ② 爆奖投稿奖励 ⑦ 日投注奖励 ③大额出款奖励 ⑧ 周投注奖励 ④真人连赢 奖励 ⑨ VIP 尊享豪礼 ⑤ 真人幸运注单 ⑩ 每日亏返 5% 🟢🟢🟢🟢🟢🟢🟢🟢 ✨🎲扫雷 6688群💫大额无忧 ✨🎲扫雷88888 群💫极速秒到 ✨🧧稳盈快三扫雷💫重磅启幕 ✨🎰稳盈B5综合娱乐 💫 一站畅玩 🧐福利来合计上押超百万U 🧐累计派发玩家盈利超 2800 万 U 😃每日一次流水红包福利 ♑ 流水红包 150U ♑ 流水红包 1500U ♑ 流水红包 15000U 🧐立即登录 B5.COM ,稳盈让娱乐更高效! 🟢🟢🟢 @eeeeee 🟢🟢🟢 @wyyl 🟢🟢🟢 B5.COM 🟢 🟢🟢 @wywy 🟢🟢🟢🟢🟢🟢🟢🟢 🟢
Signed 群管@FLL0
拼多多刁哈哈专属局 | 手气爆棚来挑战 🎉 🕹 拼单不如拼运气,豪气开局一把定乾坤! 🕹 手气来了挡不住,连中几把停不下来! 🕹 拼出属于您的辉煌局! 红包链接:https://t.me/c/2882662634/3128023 🌐 快捷导航公群: 🚀 公群830快三: https://t.me/+XduDuzZG0zExNmNk 🚀 公群807扫雷: https://t.me/+OXX19_Ln7-A2YmY0 🚀 公群8889🈵赔扫雷:https://t.me/c/2882662634/3059637 VIP每日福利大放送 : VIP群每日0:30发放红包58U/58包中奖模式,当日满足1万U流水申请进群 🥇 中红包前10名奖励66U 🥰 公群老板:@pdd88zz 🥰 公群业务员:@pdd88kf 💫 多进一个群,旺气自动升级! 💫拼单靠手速,拼运气就靠您了!🍷
Signed 群管@FLL0
🔥 【公群333 · 押金66666U 达亿娱乐·极速单骰高倍扫雷】正在派发 红包! 🧧 金额:333 USDT 🎁 数量:33 个 ⏳ 还剩:33 个 ⚡ 手快有,手慢无! 👥 仅限群成员领取
Signed 福利来钱包 @FLLQB
🔥🔥达亿国际🔥🔥单骰🈵1:1倍扫雷🎲,满倍PC2.8加拿大 达亿国际强势入驻TG福利来平台,采用TG官方骰子,任何人无法控制此随机性💯公平公正的娱乐品牌! 全网押金超300WU 达亿单骰🈵倍2.0扫雷333公群: https://t.me/+l5iETsezfvs2MmVk 达亿PC2.8🈵倍加拿大7777公群: https://t.me/+kMJRP-vVIco5NWY8 达亿PC2.0满倍加拿大2828公群: https://t.me/+thiZie8n3Wk1NjNk ———————————— 达亿集团🈵倍扫雷,🈵倍2.8加拿大 专属VIP福利 ⚡️ 特殊红包奖励,抢得越多拿得越爽! 😀【特殊红包奖励】 ✨抢到纯豹奖励⚡️⚡️⚡️⚡️ ✨抢到正顺奖 ⚡️⚡️⚡️ ✨抢到最高奖励⚡️⚡️⚡️ ✨抢到最低奖励⚡️⚡️⚡️ ============================================…
Signed 群管@FLL0
Showing the 12 most recent of 383 posts we hold for @diaosile99. 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.
Citation-graph rank — 260,343 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 2 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.
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.
“福利来红包🧧 关注我红包不错过” (@diaosile99), 30,776 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/diaosile99.
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.