Telegram RegisterThe public register of Telegram
Telegram profile photo for 主频道

Channel

主频道

@NSNB2

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

50,660subscribers

-1,821 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001978005612
TypeChannel
Username@NSNB2
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/NSNB2

Topic

Gaming — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

50,66052,48151,570.57 August 2026 — 52,481 subscribers8 August 2026 — 52,434 subscribers10 August 2026 — 52,423 subscribers11 August 2026 — 52,429 subscribers12 August 2026 — 52,439 subscribers13 August 2026 — 52,472 subscribers14 August 2026 — 52,446 subscribers16 August 2026 — 52,393 subscribers17 August 2026 — 52,314 subscribers18 August 2026 — 52,226 subscribers19 August 2026 — 52,140 subscribers20 August 2026 — 52,096 subscribers21 August 2026 — 52,030 subscribers23 August 2026 — 51,949 subscribers24 August 2026 — 51,779 subscribers25 August 2026 — 51,728 subscribers26 August 2026 — 51,689 subscribers28 August 2026 — 51,655 subscribers29 August 2026 — 51,602 subscribers30 August 2026 — 51,556 subscribers30 August 2026 — 51,504 subscribers31 August 2026 — 51,449 subscribers1 September 2026 — 51,396 subscribers3 September 2026 — 51,334 subscribers4 September 2026 — 51,269 subscribers7 September 2026 — 51,138 subscribers10 September 2026 — 50,977 subscribers12 September 2026 — 50,868 subscribers14 September 2026 — 50,815 subscribers16 September 2026 — 50,777 subscribers18 September 2026 — 50,660 subscribers7 August 202618 September 2026
31 measurements spanning 42 days, net -1,821. 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 50,387–52,754 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
18 Sept 2026, 11:3650,660-117
16 Sept 2026, 04:2250,777-38
14 Sept 2026, 09:0050,815-53
12 Sept 2026, 15:5650,868-109
10 Sept 2026, 17:4050,977-161
7 Sept 2026, 14:5651,138-131
4 Sept 2026, 15:1751,269-65
3 Sept 2026, 00:0751,334-62
1 Sept 2026, 20:5551,396-53
31 Aug 2026, 20:0451,449-55
30 Aug 2026, 23:3551,504-52
30 Aug 2026, 00:2451,556-46
29 Aug 2026, 00:1451,602-53
28 Aug 2026, 01:1351,655-34
26 Aug 2026, 23:0151,689-39
25 Aug 2026, 20:3451,728-51
24 Aug 2026, 19:1651,779-170
23 Aug 2026, 00:5751,949-81
21 Aug 2026, 15:3652,030-66
20 Aug 2026, 11:4852,096first reading

Engagement

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

ERR · 30 days
1.36%
avg views ÷ 50,660 subscribers
Avg views / post
690
218 posts measured
Reaction rate
1.20%
reactions ÷ views · ER floor
Posts in window
218
of 682 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 26 September 2026
Posts held682 (6 August 2026 – 26 September 2026)
Views total150,458
Reactions total1,800
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 05:46 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
≈4,690
Videos
≈59
Links
≈207

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. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 41s
Average length
25s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

4,681 reactions across 672 posts, in 7 distinct kinds. The most used accounts for 94.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4,42994.6%
❤2114.51%
🤩170.363%
👏100.214%
😘70.15%
🥰40.085%
😁30.064%

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

Measured over the 682 most recent posts we hold, published 6 August 2026 to 26 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, 11:04 UTC≈1,110 views48 reactionsread 27 September 2026

算了不想更新单解密了 终究内存还是要集体

👍39👏4🤩4❤1

26 Sept 2026, 01:19 UTC≈1,810 views11 reactionsread 27 September 2026
Photo

Photo, posted without a caption

👍10❤1

26 Sept 2026, 01:19 UTC≈1,380 views10 reactionsread 27 September 2026
Photo

Photo, posted without a caption

👍9❤1

25 Sept 2026, 13:50 UTC≈1,340 views21 reactionsread 27 September 2026
Photo

单解密配淋雨给我打爽了😍

👍20❤1

25 Sept 2026, 03:56 UTC≈1,090 views38 reactionsread 25 September 2026
File

久等了各位,因嘉豪单解密项目维护需要,经过为期不断的连续测试,目前已经没有什么问题了,临近中秋与国庆,所以我们打算开启中秋与国庆共同的公益活动,日期为9月25日到10月4日,活动期间你可以输入任意卡密登录嘉豪单解密,感谢你再次相信嘉豪单解密😀 关于测试 https://t.me/NSNB2/18451?single --------嘉豪单解密------- Version:0925 嘉豪单解密,即通过内存修改对游戏坐标进行解密或还原,使辅助程序能够正确读取坐标信息,当前版本提供一个方案,该方案解决了部分机型适配性! 适配性问题? 所有方案均完美兼容全机型,无需担心设备适配问题 开启方法与问题解决: 在大厅开启解密,提示解密成功代表解密成功 如果在大厅开启提示解密失败,进入大坝地图确认遁地后,大退游戏到大厅开解密可以解决 关于更新! 0925版 1.优化代码 反馈 @az509ody

👍29❤8😁1

25 Sept 2026, 03:37 UTC≈1,110 views15 reactionsread 25 September 2026

中秋节与国庆节为了感谢支持 我们将会开启公益模式 公益时间9月25日到10/4日 还没到期的用户将全部升级为周卡

👍15

24 Sept 2026, 16:26 UTC≈1,260 views15 reactionsread 25 September 2026
Photo

没什么问题 我提了一张配时间 自瞄打得

👍15

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

Forward network

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.

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

“主频道” (@NSNB2), 50,660 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/NSNB2.

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.