可能因为你一时的妥协选择了其他项目 但终有一天你会成为尊贵的的KC用户 🅰️ KC官方网站 KCNB69.com 🛡零手续费提卡网 点我购买 📣教程自瞄配置 点我查看 ✅KC下载链接 点我下载 ✅免费领卡活动 点我查看 ✅效果视频展示 点我查看 ✅第1次使用说明 点我查看 ⚠️保证账号和实名干净 设备黑了去刷机 裸奔ksu 无需刷入任何模块 购买后带订单截图 进售后群: @KCKF666 @KCNB6bot
👍12❤1
Signed 左飞 会员代开 @zuofei

Channel
@HTYS1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
10,140subscribers
+260 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003500406873 |
|---|---|
| Type | Channel |
| Username | @HTYS1 |
| Created | Between 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/HTYS1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 23:25 | 10,140 | +10 |
| 30 Aug 2026, 01:53 | 10,130 | +33 |
| 29 Aug 2026, 01:18 | 10,097 | +27 |
| 28 Aug 2026, 02:23 | 10,070 | +59 |
| 27 Aug 2026, 02:18 | 10,011 | +8 |
| 26 Aug 2026, 02:34 | 10,003 | -7 |
| 25 Aug 2026, 04:16 | 10,010 | +20 |
| 22 Aug 2026, 00:57 | 9,990 | -19 |
| 20 Aug 2026, 15:34 | 10,009 | +13 |
| 18 Aug 2026, 00:21 | 9,996 | +13 |
| 14 Aug 2026, 21:13 | 9,983 | +27 |
| 11 Aug 2026, 07:57 | 9,956 | +77 |
| 7 Aug 2026, 23:08 | 9,879 | -1 |
| 7 Aug 2026, 19:47 | 9,880 | first reading |
266 posts held, back to 3 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 35 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 262 of 266 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 266 (3 August 2026 – 29 August 2026) |
| Views total | 137,484 |
| Reactions total | 2,242 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 03:54 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.
Measured directly from 12 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.
2,242 reactions across 262 posts, in 21 distinct kinds. The most used accounts for 86.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,939 | 86.5% | |
| ❤ | 148 | 6.60% | |
| 🤡 | 57 | 2.54% | |
| 😍 | 34 | 1.52% | |
| 🔥 | 12 | 0.535% | |
| 🤩 | 12 | 0.535% | |
| 🤣 | 11 | 0.491% | |
| 👎 | 5 | 0.223% | |
| 👏 | 4 | 0.178% | |
| ❤🔥 | 3 | 0.134% | |
| 😱 | 3 | 0.134% | |
| 🌚 | 2 | 0.089% | |
| 😭 | 2 | 0.089% | |
| 🤮 | 2 | 0.089% | |
| 🤷♂ | 2 | 0.089% | |
| 💩 | 1 | 0.045% | |
| 🕊 | 1 | 0.045% | |
| 😇 | 1 | 0.045% | |
| 🤔 | 1 | 0.045% | |
| 🥰 | 1 | 0.045% | |
| 1 further kind | 1 | 0.045% |
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 262 of the 266 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 2,242reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 266 most recent posts we hold, published 3 August 2026 to 29 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.
可能因为你一时的妥协选择了其他项目 但终有一天你会成为尊贵的的KC用户 🅰️ KC官方网站 KCNB69.com 🛡零手续费提卡网 点我购买 📣教程自瞄配置 点我查看 ✅KC下载链接 点我下载 ✅免费领卡活动 点我查看 ✅效果视频展示 点我查看 ✅第1次使用说明 点我查看 ⚠️保证账号和实名干净 设备黑了去刷机 裸奔ksu 无需刷入任何模块 购买后带订单截图 进售后群: @KCKF666 @KCNB6bot
👍12❤1
Signed 左飞 会员代开 @zuofei
🏅No1飞机推荐赚钱项目现已整理可自行选择 1️⃣ 快手/抖音代发全网最高100元一单 2️⃣ 采集商家码0本金90元/个 3️⃣ 车辆号牌采集0押金 100元/车 4️⃣ 店铺门头采集0押金 80元/店 5️⃣ 投放充电宝0押金150元/个 6️⃣ 被骗了别急免费开户/轰炸三次0费用 7️⃣ 免费公益直装/美化/破解/卡密点我 8️⃣ 飞机拉新项目 0押0本 30元一单 (注:以上都是有担保押金场地 可以放心交易 项目均不需要押金 有押金让你先给钱的都是骗子) 【点击查看结账凭证】 【抢红包🧧入口群】
👍12❤2
😍主要是你的项目太好玩了,也稳定
👍14
Signed 🇭 🇹 🇾
1.KC独家硬件断点追踪,并非市面上的过检测断点 2. Hook HAL 陀螺仪技术,直接利用设备本身的陀螺仪传感器 不动内存 3.最新的解密 账号被加密了也可以使用,在绘制设置那里有解密 4.巡查预警 算法无后 露手模式 超多功能等你探索 支持😢和平精英 🙈PUBG五服 认准唯一卡网 点我查看使用教程 https://luoye.yjsfk.cn/shop/sss 购买后带订单截图 进售后群: @KCKF666
👍9❤1
Signed 左飞 会员代开 @zuofei
🏅No1飞机推荐赚钱项目现已整理可自行选择 1️⃣ 快手/抖音代发全网最高100元一单 2️⃣ 采集商家码0本金90元/个 3️⃣ 车辆号牌采集0押金 100元/车 4️⃣ 店铺门头采集0押金 80元/店 5️⃣ 投放充电宝0押金150元/个 6️⃣ 被骗了别急免费开户/轰炸三次0费用 7️⃣ 免费公益直装/美化/破解/卡密点我 8️⃣ 飞机拉新项目 0押0本 30元一单 (注:以上都是有担保押金场地 可以放心交易 项目均不需要押金 有押金让你先给钱的都是骗子) 【点击查看结账凭证】 【抢红包🧧入口群】
👍8
HTY和平内透V2 适配游戏:🇨🇳和平精英新赛季 人物红色内透 可实现300米内 HDR画质解锁人物发光 内透颜色 粉色 近点为头远点全显示 转发各频道转发的越快更新的越快 文件更新主频道 @HTYS1 已上传网盘→网盘下载
👍20❤1
Signed 🇭 🇹 🇾
🔥🥰HERO免费开户助手🥰🔥 ✅开户专用✅ ✅HERO户籍猎手✅ 安装包下载链接 https://wwapk.lanzouq.com/itrGg3xzsllc 密码:8888 🌈支持免费查询:手机号、身份证、QQ号、微信号、银行卡、车牌号、邮箱、贴吧ID、微博ID、钉钉、快手、闲鱼号、网易云ID、脸书、推特、IMEI。涵括多元档案信息。支持模糊身份证、手机号补齐,支持全国猎魔 👉😀永久公益社工库😀👈 ♥️认准唯一100K频道 其余仿冒♥️ 唯一权威官方频道 t.me/PLCOINP/8 😊👍频道主唯一认准官方猎手
👍8❤1
Signed ❂ 频道主全网收管理@oouo888
基本 全枪+配件 美化
👍14🔥2❤1🥰1
Signed 🇭 🇹 🇾
🏅No1飞机推荐赚钱项目现已整理可自行选择 1️⃣ 快手/抖音代发全网最高100元一单 2️⃣ 采集商家码0本金90元/个 3️⃣ 车辆号牌采集0押金 100元/车 4️⃣ 店铺门头采集0押金 80元/店 5️⃣ 投放充电宝0押金150元/个 6️⃣ 被骗了别急免费开户/轰炸三次0费用 7️⃣ 免费公益直装/美化/破解/卡密点我 8️⃣ 飞机拉新项目 0押0本 30元一单 (注:以上都是有担保押金场地 可以放心交易 项目均不需要押金 有押金让你先给钱的都是骗子) 【点击查看结账凭证】 【抢红包🧧入口群】
👍12❤2
背起了行囊
👍11❤2
Signed 🇭 🇹 🇾
文件圈有个规矩 别人负责泛滥文件 你负责2改泛滥的文件 然后你在把2改好的泛滥文件在收费 别人在购买你的付费2改泛滥文件在泛滥 😋
👍18❤1
Signed 🇭 🇹 🇾
KC两年老牌项目 实力铸长久 支持 🎮 和平精英 🎮 PUBG五服 🅰️ KC官方网站 KCNB69.com 🅰️核心三大功能 1️⃣内核级硬件断点 2️⃣Jolt模型漏打 3️⃣Hook HAL陀螺仪 ✅适配性 (采用独家驱动) ⚠️支持4.1到6.12(6.12比6.6大) ⭐其他亮点功能 ✈️迫击炮精确瞄准地图雷达 ✈️独家算法解密不动内存 ✈️投掷物抛物线预测 ✅算法无后 ✅烟雾漏打 ✅巡查预警 ✅露手模式 ❤️适配全外设 ❤️全枪械独立压枪 ✅支持安卓10-16录屏 直播 投屏 (别人能看到你的科🐔 可关闭) 🔥不吹牛逼 不骗人 超多功能等你探索 加入频道获取更多功能 @KCNB69 加入频道获取更多功能 @KCNB69 加入频道获取更多功能 @KCNB69
👍11
Signed 左飞 会员代开 @zuofei
Showing the 12 most recent of 266 posts we hold for @HTYS1. 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.
@HTYS1 edited 8 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 684,999 of 1,627,445entries 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.
@HTYS1 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“HTY改文件频道” (@HTYS1), 10,140 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/HTYS1.
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.