Telegram RegisterThe public register of Telegram
Telegram profile photo for 江南のTG资源频道

Channel

江南のTG资源频道

@GJN003

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

3,212subscribers

+2,954 since we began measuring on 10 September 2026

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

Register entry

Telegram ID-1003929242095
TypeChannel
Username@GJN003
Created17 June 2026 — measured — dated from the channel’s first post
First recorded10 September 2026
Last confirmed live6 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/GJN003

Topic

Hacking & security — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 the other topics.

Growth

2583,2121,73510 September 2026 — 258 subscribers10 September 2026 — 258 subscribers12 September 2026 — 392 subscribers25 September 2026 — 1,448 subscribers4 October 2026 — 2,062 subscribers11 October 2026 — 2,324 subscribers14 October 2026 — 2,426 subscribers18 October 2026 — 2,516 subscribers21 October 2026 — 2,614 subscribers24 October 2026 — 2,745 subscribers27 October 2026 — 2,868 subscribers30 October 2026 — 3,007 subscribers3 November 2026 — 3,128 subscribers6 November 2026 — 3,212 subscribers10 September 20266 November 2026
14 measurements spanning 57 days, net +2,954. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Nov 2026, 02:453,212+84
3 Nov 2026, 01:513,128+121
30 Oct 2026, 18:303,007+139
27 Oct 2026, 16:092,868+123
24 Oct 2026, 18:162,745+131
21 Oct 2026, 20:012,614+98
18 Oct 2026, 07:062,516+90
14 Oct 2026, 21:192,426+102
11 Oct 2026, 05:582,324+262
4 Oct 2026, 19:422,062+614
25 Sept 2026, 07:401,448+1,056
12 Sept 2026, 04:01392+134
10 Sept 2026, 06:22258no change
10 Sept 2026, 05:47258first reading

Engagement

5 posts held, back to 17 June 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 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 10 September 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

5 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 60.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤360.0%
😁240.0%

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

Measured over the 5 most recent posts we hold, published 17 June 2026 to 10 September 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

7 Sept 2026, 20:51 UTC610 views3 reactionsread 10 September 2026

《VPN机场》 速度快,节点多(暂时无) TG/飞机内置VPN代理: 节点1: https://t.me/socks?server=82.27.116.154&port=13678&user=3412642c7931&pass=28874dea-8adf-4214-a2af-13bff93b652b 节点2: https://t.me/socks?server=207.57.132.36&port=53961&user=840352a0512e&pass=3ad78074-a22f-4b5c-8ff0-ed284a6cf58b (点一下即可链接;时不时会更新,更新了频道会通知) 个人创建:飞机内置VPN代理链接: https://t.me/guandaili2bot?start=ref_7454825429 《VPN代理QQ群》用于:提醒节点变动

😁2❤1

7 Sept 2026, 20:51 UTC609 views1 reactionsread 10 September 2026
Photo

👋江南の频道(不是以下的 就是假冒的) ———————————————————-- ①江南のROOT资源频道:https://t.me/LFIA000 ROOT资源频道 主要更新: 玩机频道,玩机文件,环境文件 一键隐藏,三绿key密钥 ②江南の内核资源频道:https://t.me/GJN001 内核资源频道 主要更新: 频道收集,驱动大全,清理文件 公益项目推荐 ,收费项目推荐 内核项目收集 ,以及养号教程 ④江南の二游推荐频道:https://t.me/GJN002 二游资源频道 主要更新: 推荐/收集:二游内核项目 ④江南のTG资源频道:https://t.me/GJN003 TG资源频道 主要更新: VPN机场 ⑤江南の交流群:https://t.me/GJN004 该交流群分话题讨论,具有完美讨论交流生态 注:交流群管理员满足以下条件 即可私信江南给予 条件:给江南提供有关资源 管理员后续规定: ① 不准发格机 …

❤1

7 Sept 2026, 20:51 UTC514 views1 reactionsread 10 September 2026
Photo

✪ω✪ 资源导航栏 ✪ω✪ 👋TG资源 ★★★★✪ω✪★★★★ 《TG中文包》点我 ★★★★✪ω✪★★★★ 《VPN 代理》点我 👋ROOT频道资源 ★★★★✪ω✪★★★★ 《玩机频道》点我 ★★★★✪ω✪★★★★ 《玩机文件》点我 ★★★★✪ω✪★★★★ 《隐藏环境》点我 👋内核频道资源 ★★★★✪ω✪★★★★ 《内核频道》点我 ★★★★✪ω✪★★★★ 《端口频道》点我 ★★★★✪ω✪★★★★ 《驱动频道》点我 ★★★★✪ω✪★★★★ 《清理文件》点我 👋交流群 ★★★★★✪ω✪★★★★★ 《飞机交流群》《QQ交流群》 ★★ ★《留有清白在人间》★ ★★

❤1

Showing the 5 most recent of 5 posts we hold for @GJN003. 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.

Mentions

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.

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

“江南のTG资源频道” (@GJN003), 3,212 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/GJN003.

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.