#于嫣 王者公益项目 获取驱动 作者更新日志: 适配安卓17 修复部分玩家安卓16以上 开启触摸会出现卡屏情况 适配体验服最新版本 公益交流专区及拉闸交流专区
👍5❤1
Signed Mr. Ge 戈江南

Channel
@GJN001
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
11,752subscribers
+932 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1004411256781 |
|---|---|
| Type | Channel |
| Username | @GJN001 |
| Description | 温暖组织 资源汇聚 推荐项目😋 ———来了就是兄弟——— 频道汇聚了市面上绝大部分: 《内核频道》《端口频道》 《驱动频道》《清理文件》 《搞机频道》《环境方案》 在置顶导航栏查看并获取资源 及推荐解密项目供兄弟们参考 注:该频道永久中立不诋毁评价任何项目 只陈述事实:和谐 特征 拉闸 拉闸时长等 如有冒犯舆论网报等,请联系我删除信息 资源频道:https://t.me/LFIA200 交流群: https://t.me/GJN004 频道主: https://t.me/GJN000 |
| Created | Between 1 June 2026 and 6 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/GJN001 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 05:46 | 11,752 | +176 |
| 13 Aug 2026, 00:24 | 11,576 | +154 |
| 12 Aug 2026, 00:42 | 11,422 | +142 |
| 11 Aug 2026, 03:36 | 11,280 | +189 |
| 10 Aug 2026, 03:41 | 11,091 | +143 |
| 9 Aug 2026, 05:21 | 10,948 | +128 |
| 8 Aug 2026, 10:03 | 10,820 | first reading |
88 posts held, back to 6 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 14 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 85 of 88 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 | 88 (6 August 2026 – 15 August 2026) |
| Views total | 301,337 |
| Reactions total | 861 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 02:17 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.
861 reactions across 85 posts, in 18 distinct kinds. The most used accounts for 69.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 599 | 69.6% | |
| ❤ | 163 | 18.9% | |
| 👎 | 24 | 2.79% | |
| 👏 | 24 | 2.79% | |
| 🤬 | 14 | 1.63% | |
| 🤮 | 11 | 1.28% | |
| 🥰 | 7 | 0.813% | |
| 👌 | 3 | 0.348% | |
| 🤣 | 3 | 0.348% | |
| 🌭 | 2 | 0.232% | |
| 🖕 | 2 | 0.232% | |
| 😁 | 2 | 0.232% | |
| 😭 | 2 | 0.232% | |
| 🍌 | 1 | 0.116% | |
| 😍 | 1 | 0.116% | |
| 😨 | 1 | 0.116% | |
| 🤔 | 1 | 0.116% | |
| 🥴 | 1 | 0.116% |
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 88 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 861reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 88 most recent posts we hold, published 6 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.
#于嫣 王者公益项目 获取驱动 作者更新日志: 适配安卓17 修复部分玩家安卓16以上 开启触摸会出现卡屏情况 适配体验服最新版本 公益交流专区及拉闸交流专区
👍5❤1
Signed Mr. Ge 戈江南
#Fuzz 瓦手公益解密项目 解密方式:未知 直链下载 作者更新日志: 修复漏打模型部分设备加载失败问题 卡密随便输入 拉闸了或者解密和谐了告诉我 公益交流专区及拉闸交流专区
❤3👍3
这次更新,好像确实解决了网波🍟 在现在这个解密大概率拉闸的时候 我觉得可以试试:双端+公益项目
❤3
Signed Mr. Ge 戈江南
昏迷醒了👋
👍10
Signed Mr. Ge 戈江南
声明...
👍10❤3
Signed Mr. Ge 戈江南
不是我找的解密项目不好 是现在大部分解密项目都这样 知名的内核作者如:enen,林羽 现在都不这么更新三角洲的解密了 我只能找一些新作者写的三角洲解密项目 这个频道开讨论群 就是为了讨论新项目拉不拉闸,解密有没有效果等等问题 这么多项目,我不可能每一款都去测试的,何况我的时间也不允许 再说测试了多半也没有参考价值,因为根本判断不了是不是算法/坐标
👍13❤7
Signed Mr. Ge 戈江南
#灰灰 使命召唤公益项目 直链下载 作者更新日志: 更新无模块和内核陀螺仪自瞄 对接其他驱动 卡密: HHO931FCD7CB50A142F5D765953C2F84 拉闸了或者解密和谐了告诉我 公益交流专区及拉闸交流专区
👍6❤1
Signed Mr. Ge 戈江南
猜内核作者🙈 在那个内核作者天才遍地的时代 却有一个作者天天更新海岛奇兵 但现在仍然很多人都盼着他更新
👍13
Signed Mr. Ge 戈江南
推荐栏的游戏够了吧🌚 还需要添加什么游戏吗🧐
👍11
Signed Mr. Ge 戈江南
重新上传了,重新下载即可👋 我之前上传错了,没群友告诉我 我刚才去打暗区才发现的 🌚🌚
👍9❤4
Signed Mr. Ge 戈江南
#库洛米 三角洲公益解密项目 解密方式:作者说是算法解密 作者介绍: 算法解密一:实时坐标同步 游戏把人物位置处理好以后; 程序同步读取最新坐标,再对应到具体人物身上 算法解密二:移动队列解析 持续解析人物的移动更新队列; 根据人物标识匹配坐标,并同步到绘制信息 卡密:KULUOMI_Y6D5E7AE73A437E75DB79FDF 拉闸了或者解密和谐了告诉我 公益交流专区及拉闸交流专区
👍5❤2
Signed Mr. Ge 戈江南
#iUi葫芦娃 和平公益项目 解密方式:未知 获取驱动 作者更新日志: 1.对接kairos驱动、适配最新GT驱动 2.优化和解决一些问题 公益交流专区及拉闸交流专区
👍6❤1
Signed Mr. Ge 戈江南
Showing the 12 most recent of 88 posts we hold for @GJN001. 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.
@GJN001 edited 2 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 — 274,862 of 1,350,102entries 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 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“江南の推荐频道” (@GJN001), 11,752 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/GJN001.
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.