Channel
@JYNH6
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,463subscribers
-26 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001049181517 |
|---|---|
| Type | Channel |
| Username | @JYNH6 |
| Created | Between 1 February 2016 and 30 November 2016— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/JYNH6 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 19:47 | 4,463 | -14 |
| 27 Aug 2026, 15:42 | 4,477 | -4 |
| 24 Aug 2026, 07:18 | 4,481 | -8 |
| 23 Aug 2026, 09:00 | 4,489 | first reading |
20 posts held, back to 1 March 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 pageof 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 23 August 2026 |
|---|---|
| Posts held | 20 (1 March 2026 – 23 August 2026) |
| Views total | 748 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Aug 2026, 09:00 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.
218 reactions across 16 posts, in 7 distinct kinds. The most used accounts for 77.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 169 | 77.5% | |
| 👍 | 31 | 14.2% | |
| 😱 | 10 | 4.59% | |
| 🤯 | 3 | 1.38% | |
| 🍌 | 2 | 0.917% | |
| 🥰 | 2 | 0.917% | |
| 🥴 | 1 | 0.459% |
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 16 of the 20 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 218reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 1 March 2026 to 23 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.
🔥极域_Doro硬件断点追锁项目 核心亮点： ✅独家驱动自隐藏全部痕迹 ✅独家算法解密和闪框解密 ✅Phys X模型漏打不动内存 ✅内核级陀螺仪自瞄(非系统) ✅内核级硬件断点追踪(无过检) ✅内核级权重中心追踪（无异常） ✅支持5-6系天玑/骁龙设备 ➡️自瞄：载具不锁/掉血自瞄/烟雾不瞄 ➡️追踪：各种枪械类可单独调试配置 ➡️快捷控件：自瞄开关/追踪开关 ➡️自保控件：自动400范围100概率 ➡️露手模式：小白点看不出任何绘制 下载链接点我下载链接点我 提取码：Doro 🌟官方频道：https://t.me/Doro789 🌟官方频道：https://t.me/JYNH6
打算更新了
有人吗
👍20❤1
已经适配1.37版本
🔥极域和平公益内核 ✅适配1.37夏日版本 😄精品无问题源 😃无模块陀螺仪自瞄 😄内核级触摸自瞄 😃掩体模型漏打 😄采用独家算法陀螺仪自瞄 😃自瞄分为软锁/强锁两款 😄自由拉伸UI大小 😃无任何内存功能使 😄暂时无法添加追踪（在研究） 🥰对接rt全系列部分驱动 😀加入频道：@JYNH6
❤9
陀螺仪自瞄超榜30多分 可惜实名黑了无法封神
❤13
⭐极域葫芦娃 陀螺仪漏打🇨🇳 ✅修复部分人刷驱动没效果 ✅修复掉悬浮窗问题 ✅修复驱动刷入后内核不读取 ✅触摸更换为内核级触摸 🤔有bug记得反馈我会看也会修复 ➡️ https://t.me/JYNH6 ⬅️ 😀加入上方官方频道😀
❤12
如果使用非官方正常卡密无法正常启动内核 支持你们使用正版和破解版测试
❤2
解密没效果卸载三角洲重新下载
✅极域八宝粥公益算法解密内核 ✅单透版本 目前无其他功能 ✅解密不偏不漏无延迟(除60帧外) ✅独家KPM模块驱动隐藏性MAX ✅使用算法解密需刷独家驱动 ❤️解密分为算法解密和替代解密 ✅算法解密为算法不动任何内存 ✅替代解密为过检测内存解密 ✅部分四系无法使用算法解密 😙⚠️刷KPM模块驱动的基本常识 ❗️KPM模块阿尔法面具也可以刷 😭免解BL设备禁止使用(无限重启) 😭有些设备刷模块时有个嵌入按钮 禁止嵌入 禁止嵌入 (点击后果自负) ✅其他设备正常使用即可 公益卡密：@JYNH6 反馈发送：@vip_sgnb 官方频道：@JYNH6 目前公益使用 不宣传=开启收费😭
❤13
⭐Doro&极域伪葫芦娃（陀螺仪漏打） ⭐币子特供葫芦娃3k源 🥰全自动注入解密 🥰陀螺仪漏打自瞄 🥰适配率高CPU占用低 🥰软锁/平滑/强锁自定义挑选 🥰漏哪打哪指哪打哪 🥰雪花背景UI 🥰触摸/陀螺仪自定义调试 🥰对接了部分世面好用的驱动 🌟点我查看此版本内核UI 😡4系执行自动转换张豪全防 🎁加入频道：@JYNH6 🎁加入频道：@JYNH6 🎁加入频道：@JYNH6 👿反馈/bug找我 @vip_sgnb
❤7
公益那么久，支持一下赞助版吧
❤7
Showing the 12 most recent of 20 posts we hold for @JYNH6. 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 — 846,999 of 1,627,068entries 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 5 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“极域内核官方频道” (@JYNH6), 4,463 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/JYNH6.
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.