Telegram RegisterThe public register of Telegram
Telegram profile photo for 江南の内核资源站

Channel

江南の内核资源站

@GJN001

On this record: Topic · Observations · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Polls · Citations · Handles named that no longer answer · Cite this entry

20,170subscribers

+9,350 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1004411256781
TypeChannel
Username@GJN001
CreatedBetween 1 June 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live19 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/GJN001

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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.

Observations

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.

Views per post sit far above this size band

11,900 average views per post against 20,170 subscribers — an engagement rate of 58.8%. Across the 1,861 registered channels in the same cohort — 10,002–31,616 subscribers, posting mainly in Chinese — the middle half sit between 1.58% and 8.36%, with a median of 3.52%.

What this was computed from
Window30 days (23 August 2026 22 September 2026)
Posts measured10 of 10 published in the window (0 exact, 10 rounded by Telegram)
Views totalled118,610
Mature posts only58.8% over 10 posts read at least 24h after publication
Subscribers20,170 measured 19 September 2026
Cohortb10000:zho · 1,861 channels · p10 0.474% · p25 1.58% · p50 3.52% · p75 8.36% · p90 16.2%
Position in cohort99.409th percentile · 16.7× the cohort median
Uncertainty±0.157% of the figure, from Telegram’s rounding
Post languageChinese · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 22 September 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.

Growth

10,82020,17015,4958 August 2026 — 10,820 subscribers9 August 2026 — 10,948 subscribers10 August 2026 — 11,091 subscribers11 August 2026 — 11,280 subscribers12 August 2026 — 11,422 subscribers13 August 2026 — 11,576 subscribers14 August 2026 — 11,752 subscribers15 August 2026 — 11,957 subscribers17 August 2026 — 12,190 subscribers18 August 2026 — 12,297 subscribers19 August 2026 — 12,440 subscribers20 August 2026 — 12,650 subscribers21 August 2026 — 12,829 subscribers22 August 2026 — 13,124 subscribers24 August 2026 — 13,481 subscribers25 August 2026 — 13,722 subscribers26 August 2026 — 13,944 subscribers27 August 2026 — 14,151 subscribers28 August 2026 — 14,304 subscribers29 August 2026 — 14,487 subscribers30 August 2026 — 14,661 subscribers31 August 2026 — 14,806 subscribers1 September 2026 — 14,967 subscribers2 September 2026 — 15,144 subscribers3 September 2026 — 15,306 subscribers5 September 2026 — 15,648 subscribers9 September 2026 — 16,204 subscribers11 September 2026 — 16,929 subscribers13 September 2026 — 17,610 subscribers15 September 2026 — 18,275 subscribers17 September 2026 — 19,031 subscribers19 September 2026 — 20,170 subscribers8 August 202619 September 2026
32 measurements spanning 42 days, net +9,350. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 9,418–21,573 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
19 Sept 2026, 16:3620,170+1,139
17 Sept 2026, 03:2119,031+756
15 Sept 2026, 07:1518,275+665
13 Sept 2026, 13:3917,610+681
11 Sept 2026, 17:1916,929+725
9 Sept 2026, 00:1816,204+556
5 Sept 2026, 15:1815,648+342
3 Sept 2026, 13:0115,306+162
2 Sept 2026, 05:5515,144+177
1 Sept 2026, 03:5614,967+161
31 Aug 2026, 03:0414,806+145
30 Aug 2026, 05:4414,661+174
29 Aug 2026, 07:0314,487+183
28 Aug 2026, 10:1814,304+153
27 Aug 2026, 13:1514,151+207
26 Aug 2026, 11:1313,944+222
25 Aug 2026, 12:2313,722+241
24 Aug 2026, 13:3713,481+357
22 Aug 2026, 22:1413,124+295
21 Aug 2026, 12:4212,829first reading

Engagement

128 posts held, back to 6 August 2026the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 48 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
58.8%
avg views ÷ 20,170 subscribers
Avg views / post
11,900
10 posts measured
Reaction rate
0.5%
reactions ÷ views · ER floor
Posts in window
10
of 128 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 31 August 2026
Posts held128 (6 August 202631 August 2026)
Views total118,610
Reactions total593
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 10:56 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.

Reaction mix

2,448 reactions across 124 posts, in 26 distinct kinds. The most used accounts for 58.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,44258.9%
44318.1%
😭37315.2%
👎381.55%
👏251.02%
💔160.654%
💩160.654%
🤬140.572%
🤮110.449%
😍100.408%
🫡90.368%
🤡70.286%
🥰70.286%
🖕50.204%
😱40.163%
🤣40.163%
🦄40.163%
👌30.123%
😨30.123%
🤓30.123%
6 further kinds110.449%

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 124 of the 128 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,448 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 128 most recent posts we hold, published 6 August 2026 to 31 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.

Recent posts

31 Aug 2026, 21:56 UTC≈5,510 views177 reactionsread 3 September 2026

最近刷贴吧,刷多了,我来讲讲我的故事吧 我今年20了,性杨,身份证44010020060115xxxx 13岁,资产:8k左右 2019年的记忆很模糊/磨损 记得那时候是初二在河源,江南我阿,初一初二那两年,被欺负得不少,学校里面的小混混不占少数,我虽无意招惹,但是总被骚扰并殴打;想着告诉老师处理,但老师却置之不理,敷衍了事还名言称:为什么不打别人就打你,这句话我记了三年;初二下学期,我去找了我的叔叔,他得知了之后并未向老师理论,而是以其人之道换之其身,叫我放学时跟着他们,好在四线城市的农村镇上,地方不大,监控也少,他们被教训了一顿后都安分了下来 我很崇拜我的叔叔,他是我们家族非常富有之人,可惜和我家父矛盾很深,帮助不了我家庭,但愿意帮助我这位后人:12岁教我下载了飞机,我们常年用飞机联系;13岁给我介绍了他的朋友带我做灰产/黑产(洗米) 后续在学校几乎天天混混饿饿度日,课间会跟朋友讲游戏里的条条框框,周末会带朋友/同学

👍76😭5432💩11🤓3👏1

Signed Mr. Ge 戈江南

29 Aug 2026, 13:57 UTC≈8,590 views37 reactionsread 3 September 2026
File

👋更新内容: 从上号前改名为换号前 毕竟主要作用是换号不传染 #清理崩溃日志 #清理Gamelet游戏日志 #清理Gamelet内置网页cookie缓存 #清理Gamelet网页归档缓存 #清理用户网页日志 #清理网页界面 #清理更多缓存 #清理三配置

👍2412🖕1

Signed Mr. Ge 戈江南

29 Aug 2026, 10:23 UTC≈8,810 views33 reactionsread 3 September 2026
File

File, posted without a caption

👍294

Signed Mr. Ge 戈江南

26 Aug 2026, 21:35 UTC≈13,400 views36 reactionsread 3 September 2026
File

#驱动大全【江南收集9.0】 1.0 直链下载 收集更新日志: 时间驱动旧版👉时间驱动新版 光头强旧版👉光头强新版 TGV1.0👉TGv1.1 驱动交流专区 驱动交流专区

👍2410🍌1🔥1

Signed Mr. Ge 戈江南

26 Aug 2026, 12:31 UTC≈13,300 views75 reactionsread 3 September 2026

《搞机频道》《环境方案》《VPN 代理》 得等主频道回归,因为全部需要重新整理😫

👍607👎4🦄4

Signed Mr. Ge 戈江南

26 Aug 2026, 06:52 UTC≈13,600 views36 reactionsread 3 September 2026
Photo

我在飞机退网期间有很多骗子冒充我,别上当了 我的账号都是挂着频道的,没挂的都是骗子

👍259😍2

Signed Mr. Ge 戈江南

24 Aug 2026, 18:04 UTC≈14,100 views59 reactionsread 3 September 2026
File

👋更新内容:增加清理安卓设备标记性质

👍4118

Signed Mr. Ge 戈江南

24 Aug 2026, 12:22 UTC≈13,600 views32 reactionsread 3 September 2026

需要的还是可以找我做的,我只是被傻逼气到了 https://t.me/GJN001/515 加QQ群 找戈江南,qq号为3090609895

👍275

Signed Mr. Ge 戈江南

24 Aug 2026, 10:15 UTC≈13,500 views43 reactionsread 3 September 2026

不接不聚了,这tm可以退款 都有人喷啊,真的是吃力不讨好

👍358

Signed Mr. Ge 戈江南

24 Aug 2026, 07:43 UTC≈14,200 views65 reactionsread 3 September 2026

怪不得做环境手子的天天喊苦,原来是傻子太多了 (我也是被折磨了到快死了) 我这三天接了几个就出现了6个不同的情况 1.KSU或mt管理器挂后台 后果:王者闪框 2.问题不自我排查,一口咬定是你的原因 如:三角洲封三方了,你做到环境真不行,我之前都不会 3.不说实话 如:问他清理没有,说清理了,远程一看清理了个蛋 4.黑设备裸奔不了 名言:别人行,你不行 5.不清理直接换号 名言:为什么我换什么号都聚/闪了,你的环境不行 6.部分不给反馈,有没有解决说也不说 (如果是这上面的6种情况,我觉得做环境手子挺冤屈的) 过环境的模块无非就是那几个:zygisk、LSP、HMA、TEES/TS、防扫盘:就单纯装这几个:白设备可以裸奔,黑设备裸奔不了 这就有人问了:为什么会有白设备/黑设备的说法: 因为会检查你的硬件信息;你不信,你可以去改个华为机型以及麒麟芯片,是不是就可以裸奔了,这是因为华为是绝对的白设备) (但是现在改U,只要三角

38👍27

Signed Mr. Ge 戈江南

22 Aug 2026, 10:28 UTC≈13,900 views44 reactionsread 3 September 2026

要是完全想要也可以🧐 我应该有个办法可以🤓

👍32😍75

Signed Mr. Ge 戈江南

22 Aug 2026, 10:10 UTC≈14,100 views36 reactionsread 3 September 2026

这么怎么多要求要做三角洲裸奔环境呢😫 我之前都说了,三角洲会标记SOC的 骁龙被标记了刷机都没用(可能是骁龙开源太多了)

👍305🤣1

Signed Mr. Ge 戈江南

Showing the 12 most recent of 128 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.

Posts edited after publishing

@GJN001 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.

First edit seen
8 August 2026
Most recent edit
28 August 2026

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

15 Aug 2026, 11:51 UTCAnonymous Poll272 voters

以后反馈比较多的,需要加上<群友反馈>吗

  1. 加上89%
  2. 不加上11%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 128 most recent posts we hold, published 6 August 2026 to 31 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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.

Mentions

Named by 4 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.

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.

Cite this entry

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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“江南の内核资源站” (@GJN001), 20,170 subscribers as measured 19 September 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.