🤩SEVEN和平付费配置3.0 支持和平全部模式 安卓全部机型 🌊无封号风险 乱打即可 封禁10x赔偿 ❤️功能列表: 漏打范围1.0 子弹聚集MAX 魔法子弹1.0 减少后坐力抖动 子弹80%在头部 腰射触发自动瞄准 开镜人物吸附 打击效果 画面效果最舒适 超低延迟MAX 144帧率露头就秒 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #SEVEN
👍3😍1

Channel
@HUIYIYYDS6
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
23,781subscribers
+521 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002401850159 |
|---|---|
| Type | Channel |
| Username | @HUIYIYYDS6 |
| Description | 此账号已由张汉卿转交于随意 有事情也可以去找他: @qxgy88666 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/HUIYIYYDS6 |
Gaming — 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 53% 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 4 other registered channels. They sit inside a group of 8 channels that share the same post bodies with each other. 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 |
|---|---|---|---|
| @HUIYIYYDS6/32685 · this entry5 Aug 2026, 00:43 UTC | @LMY1015/320345 Aug 2026, 00:45 UTC | 1.00 | 2 minutes |
| @HUIYIYYDS6/32690 · this entry5 Aug 2026, 00:43 UTC | @LMY1015/320395 Aug 2026, 00:45 UTC | 1.00 | 2 minutes |
| @HUIYIYYDS6/32691 · this entry5 Aug 2026, 00:43 UTC | @LMY1015/320405 Aug 2026, 00:45 UTC | 1.00 | 2 minutes |
| @HUIYIYYDS6/32695 · this entry5 Aug 2026, 00:43 UTC | @LMY1015/320455 Aug 2026, 00:45 UTC | 1.00 | 2 minutes |
| @HUIYIYYDS6/32723 · this entry7 Aug 2026, 01:32 UTC | @LMY1015/321607 Aug 2026, 01:34 UTC | 1.00 | 2 minutes |
| @HUIYIYYDS6/32725 · this entry7 Aug 2026, 01:32 UTC | @LMY1015/321627 Aug 2026, 01:34 UTC | 1.00 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @LMY1015 | 24 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (24–0) |
| @LMGWJWD6 | 24 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (24–0) |
| @wjhshsne | 18 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (18–0) |
| @XiaoxueVkernel6 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (4–2) |
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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 31 comparable posts for this entry, running 5 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 8, the earliest publisher we hold is @HLWNHNB7. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_mutual · clone_source, last confirmed 8 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 7 other registered channels, 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 |
|---|---|---|
| 12 Aug 2026, 21:28 | 23,781 | +58 |
| 11 Aug 2026, 22:42 | 23,723 | +65 |
| 10 Aug 2026, 20:31 | 23,658 | +71 |
| 9 Aug 2026, 23:36 | 23,587 | +73 |
| 9 Aug 2026, 01:21 | 23,514 | +61 |
| 8 Aug 2026, 03:31 | 23,453 | +78 |
| 7 Aug 2026, 02:14 | 23,375 | +111 |
| 6 Aug 2026, 05:44 | 23,264 | +4 |
| 6 Aug 2026, 03:49 | 23,260 | first reading |
85 posts held, back to 5 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 20 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.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 85 (5 August 2026 – 12 August 2026) |
| Views total | 33,302 |
| Reactions total | 393 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 22:44 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 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 19 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.
358 reactions across 70 posts, in 6 distinct kinds. The most used accounts for 73.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 264 | 73.7% | |
| 😍 | 39 | 10.9% | |
| 🤓 | 29 | 8.10% | |
| ❤ | 23 | 6.42% | |
| 🤡 | 2 | 0.559% | |
| 😘 | 1 | 0.279% |
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 85 of the 85 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 393reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 85 most recent posts we hold, published 5 August 2026 to 12 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.
🤩SEVEN和平付费配置3.0 支持和平全部模式 安卓全部机型 🌊无封号风险 乱打即可 封禁10x赔偿 ❤️功能列表: 漏打范围1.0 子弹聚集MAX 魔法子弹1.0 减少后坐力抖动 子弹80%在头部 腰射触发自动瞄准 开镜人物吸附 打击效果 画面效果最舒适 超低延迟MAX 144帧率露头就秒 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #SEVEN
👍3😍1
🤩小黄新赛季人物红色内透V38【HDR发光】 ✅游戏名称:和平精英🎮 ✅设备要求:无需root ‼️人物内透最远可实现200米 ‼️经典地铁绿洲模式都有效果 ✅体质差的=搭配端口 ✅体质好的=大厅界面导入原版 👍范围区域=无 👍功能区域=无 👍广角区域=小广角 ❤️头部天线区域: ✅内透颜色=[红色] ✅全部人物==头部内透 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #小黄
👍3😍1
🤩超人强至尊版美化V1️⃣6️⃣7️⃣ ✅修复秃头: 头发2+颜色4=修复秃头 ✅仿PUBG头发=头发8+颜色1 ✅地铁完美MG3 ✅地铁流光效果 ✅龙吟MK14地铁打击 ✅机瞄改红点 红点改红点 ✅红装特效: 湖蓝色名流帽子=跳跃特效 湖蓝色名流眼镜=冲刺特效 湖蓝色名流鞋子=打药特效 湖蓝色名流裤子=翻越特效 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #超人强
👍4😍1
🤩喜鹤新版本无敌PAK V9[豪华版] 🗃️支持功能[天天开心]↓ 🤓全模式单软锁自瞄 🗃️支持枪械[天天开心]↓ 👑AKM 👑AUG 👑M416 👑M762 👑SCARL 👑GROZA 👑卓越ACE 👑卓越PKM 👑精致DBS 👑卓越喜鹤 👑[卓越枪械为共享枪械] 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #喜鹤
👍3😍1
🤩小吴付费范围配置🔤1️⃣3️⃣(巅峰之作) ❤️支持功能: ✅350亮度视频无亮度=作者把亮度调了 ✅亮度动态模型范围 ✅1.4超大无任何减伤范围 ✅子追 ✅子追距离500米 ✅仿内核自瞄 ✅120度平滑自瞄 ✅内置多款设备范围增强 ✅144帧率+锁针+极清🔥 ✅超体英雄属性范围增强 ✅范围拓展 ✅独家裸奔广角 ✅效果步枪枪械增强 ✅头部范围增大 ✅美国子弹⭐ ✅独家范围 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #小吴
👍3😍1
🤩小林至尊版美化V2️⃣3️⃣2️⃣ ✅修复秃头: 第4个颜色第1个发型=修复秃头 ✅纯金仓库+最新蹦蹦迈凯伦皮肤 ✅经典无配件+星际m4+投掷物手持 ✅普通仓库+星际m4+称号+头像框 ✅新增三款大厅动态背景图 ✅载具入场+红装语音+特殊入场 ✅新增最新传世武器 审判者骨鞭 ✅新增传世武器手持+投掷物特效 ✅红装特效: 红色运动鞋=隐藏彩蛋 湖蓝色名流=红装特效 黑色运动鞋=金龙特效 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #小林
👍4😍1
🤩霄白v103 Pro Max【暴力腰射】 ❤️核心说明: 🎲此文件是配置文件 无需ROOT 🎲无需演戏 无需搭配端口 🎲此配置精准命中敌人头部 🎲支持全部机型 效果增强 ❤️核心功能: 💜增强设备性能 💜减少所有枪械后坐力 💜启用后坐力回弹 💜减少枪械子弹散布 💜动态范围3.0(无减伤) 💜动态范围2.5(无减伤) 💜冲锋枪开镜速度加50% 💜修复弹道偏移 💜修复子弹减伤99% 💜地铁后座率降低20% 💜50米之内自动Al自瞄 💜枪械增强M416/M762/Aug/蜜獾/ 💜地铁/经典效果增强 💜部分冲锋枪降低后座60% 💜手感增强MAX自瞄 💜近战50米概率子追 💜辅助瞄准史诗级加强 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #霄白
👍3😍1
🤩沐屿止痛药 V13💊 📆:2026.8.8 作者:沐屿 💊亮度350% 💊独家算法自瞄 💊亮度+动态范围 💊人物受击范围1.45 💊射速1.0 💊继承少羽uzi跳枪准度 💊350W范围 💊弹无虚发 💊子弹会拐弯 💊子弹长大了有自己的想法 💊微魔法子弹 💊子弹发展科技强国 💊爆头率增加9527% 💊安卓15效果衰减回调 💊安卓9~16效果加强 💊支持安卓9~16 💊支持苹果iOS全系统 💊全模式通用 💊稳定性100% 🔗点击立即前往网盘下载 🔗点击立即前往网盘下载 #和平精英 #改文件 #沐屿
👍3😍1
BlackSnowKernel-77.3(最新防过期).zip 更新防过期版本 #网页雷达 ->本地云端雷达共享 ->随意拖拽 ->人物盒子 ->地图物资 ->英雄显示 ->队伍编号 ->随意放大 ->头甲显显示 #字体调节大小页面 ->头甲大小 ->骨骼粗细 ->物资大小 ->盒子大小 ->距离大小 ->名称大小 ->手持大小 地图雷达 ->显示物资 ->显示容器 ->显示玩家->显示AI ->显示技能预警 ->显示玩家骨灰盒 大地图雷达 ->大地图雷达 ->玩家 AI 雷达 ->地图高级Boss ->队伍编号显示 ->高价值物资列表 ->右侧图显高价值物资列表 ->左侧图显玩家距离 点我加入频道 😙😙😙😙😙😙😙😙 点我前往网盘下载 密码在夸克或者UC网盘 下载地址在百度 迅雷 推荐百度网盘 😙看清楚了 解压密码在夸克或者UC网盘 📣卡密随便输入
👍3😍1
三角洲.于嫣裸奔范围v2修复版.sh 卡密随便输入 不要输入1 随便输入几位数字就行了 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:8月12日更新 https://pan.xunlei.com/s/VOsYxkoAmjGIC02-xOZ0Yj5rA1?pwd=fj2m# #三角洲 #于嫣 #范围
👍5🤓1😍1
三角洲李子内部范围 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:8月12日更新 https://pan.xunlei.com/s/VOsYxkoAmjGIC02-xOZ0Yj5rA1?pwd=fj2m# #三角洲 #李子 #范围
👍5🤓1😍1
三角洲.萤石解密内核最新版 先刷驱动 等待10多秒自动出悬浮窗了 每天不定时更新公益项目 有时候不发在频道 你们保存网盘订阅链接就可以每天下载不同的新项目了 下载地址:8月12日更新 https://pan.xunlei.com/s/VOsYxkoAmjGIC02-xOZ0Yj5rA1?pwd=fj2m# #三角洲 #萤石 #内核
👍5🤓1😍1
Showing the 12 most recent of 85 posts we hold for @HUIYIYYDS6. 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 — 187,889 of 1,151,006entries 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.
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 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“苏七公益分享频道[文件泛滥][公益破解][软件分享]🇨🇳” (@HUIYIYYDS6), 23,781 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/HUIYIYYDS6.
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.