Telegram RegisterThe public register of Telegram
Telegram profile photo for GT端口通知频道

Channel

GT端口通知频道

@hdgnb11

3 usernames

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

24,483subscribers

+4,138 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002086561901
TypeChannel
Usernames@gtnb89 @hdgnb11 @zjznb11
Description不参加任何网络纷争
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held38
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/hdgnb11

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 38% 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.

Growth

20,08924,72022,404.57 August 2026 — 20,345 subscribers7 August 2026 — 20,345 subscribers8 August 2026 — 20,392 subscribers9 August 2026 — 20,431 subscribers10 August 2026 — 20,468 subscribers11 August 2026 — 20,511 subscribers12 August 2026 — 20,513 subscribers13 August 2026 — 20,569 subscribers14 August 2026 — 20,593 subscribers16 August 2026 — 20,508 subscribers16 August 2026 — 20,508 subscribers17 August 2026 — 20,499 subscribers18 August 2026 — 20,530 subscribers19 August 2026 — 20,506 subscribers20 August 2026 — 20,577 subscribers22 August 2026 — 20,751 subscribers23 August 2026 — 20,763 subscribers25 August 2026 — 20,743 subscribers25 August 2026 — 20,722 subscribers27 August 2026 — 20,704 subscribers27 August 2026 — 20,687 subscribers28 August 2026 — 20,665 subscribers29 August 2026 — 20,653 subscribers30 August 2026 — 20,642 subscribers1 September 2026 — 20,624 subscribers1 September 2026 — 20,535 subscribers3 September 2026 — 20,508 subscribers4 September 2026 — 20,490 subscribers6 September 2026 — 20,456 subscribers10 September 2026 — 20,415 subscribers12 September 2026 — 20,343 subscribers14 September 2026 — 20,263 subscribers15 September 2026 — 20,262 subscribers16 September 2026 — 24,720 subscribers17 September 2026 — 20,235 subscribers19 September 2026 — 24,663 subscribers24 September 2026 — 20,089 subscribers25 September 2026 — 24,483 subscribers24,4837 August 202625 September 2026
38 measurements spanning 49 days, net +4,138. 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 19,394–25,415 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 38
Measured (UTC)SubscribersChange
25 Sept 2026, 17:5624,483+4,394
24 Sept 2026, 22:2220,089-4,574
19 Sept 2026, 00:3924,663+4,428
17 Sept 2026, 23:1520,235-4,485
16 Sept 2026, 19:2024,720+4,458
15 Sept 2026, 15:5620,262-1
14 Sept 2026, 00:1820,263-80
12 Sept 2026, 04:2020,343-72
10 Sept 2026, 00:2120,415-41
6 Sept 2026, 15:4120,456-34
4 Sept 2026, 08:0020,490-18
3 Sept 2026, 00:1620,508-27
1 Sept 2026, 22:1520,535-89
1 Sept 2026, 00:2820,624-18
30 Aug 2026, 22:3920,642-11
29 Aug 2026, 23:2820,653-12
28 Aug 2026, 23:3420,665-22
27 Aug 2026, 22:4620,687-17
27 Aug 2026, 00:4220,704-18
25 Aug 2026, 21:2420,722first reading

Engagement

240 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 68 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.77%
avg views ÷ 24,483 subscribers
Avg views / post
432
21 posts measured
Reaction rate
1.47%
reactions ÷ views · ER floor
Posts in window
28
of 240 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 27 September 2026
Posts held240 (3 August 2026 – 27 September 2026)
Views total9,078
Reactions total133
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 11:57 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.

What this channel posts

Photos
206
Links
6

Lifetime counters from Telegram’s own channel header, read 27 September 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.

Reaction mix

1,240 reactions across 224 posts, in 16 distinct kinds. The most used accounts for 73.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍91173.5%
🤣987.90%
💩967.74%
❤433.47%
🤮423.39%
😡161.29%
😭120.968%
👌70.565%
🥰40.323%
👏20.161%
🖕20.161%
🤡20.161%
🤬20.161%
🍌10.081%
🔥10.081%
🤔10.081%

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

Measured over the 240 most recent posts we hold, published 3 August 2026 to 27 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

26 Sept 2026, 04:47 UTC368 views9 reactionsread 27 September 2026

duck更新 1.更新 udp 解密 2.修复大小地图 3.修复胸挂背包 4.修复密钥失败

👍9

24 Sept 2026, 05:31 UTC644 views16 reactionsread 27 September 2026
Photo

Photo, posted without a caption

🤮7👍4🤣3🤡2

24 Sept 2026, 04:30 UTC536 views4 reactionsread 26 September 2026

临时版 1.优化部分问题 2.有些账号出现只有近点才有人是因为被迷雾了 换个账号 3.漏打更新好了 4.移除了大地图显示因为每台每台设备分辨率不一样更起来麻烦也不怎么实用 5.此版本作为临时版使用

👍4

23 Sept 2026, 14:52 UTC575 views8 reactionsread 26 September 2026

Duck解密和谐了 等作者更新 海盗狗正常使用

🤮5👍3

Showing the 12 most recent of 240 posts we hold for @hdgnb11. 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

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

First edit seen
18 August 2026
Most recent edit
21 August 2026

Forward network

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.

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

“GT端口通知频道” (@hdgnb11), 24,483 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/hdgnb11.

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.