Telegram RegisterThe public register of Telegram

Channel

恶魔直装主频道[冲23K]

@SNKNB

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

22,088subscribers

+123 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-1003942229279
TypeChannel
Username@SNKNB
Description项目负责人 @NSNB1166 反馈,合作联系 @NSNB1166 obb频道: @EVISUTG 交流群频道: @AUGNB
CreatedBetween 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/SNKNB

Growth

21,96522,14622,055.57 August 2026 — 21,965 subscribers7 August 2026 — 21,965 subscribers7 August 2026 — 21,973 subscribers8 August 2026 — 22,040 subscribers9 August 2026 — 22,115 subscribers10 August 2026 — 22,146 subscribers11 August 2026 — 22,125 subscribers12 August 2026 — 22,088 subscribers22,0887 August 202612 August 2026
8 measurements spanning 5 days, net +123. 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 21,938–22,173 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 17:3422,088-37
11 Aug 2026, 19:3322,125-21
10 Aug 2026, 21:3122,146+31
9 Aug 2026, 19:1122,115+75
8 Aug 2026, 21:3022,040+67
7 Aug 2026, 21:5721,973+8
7 Aug 2026, 13:0021,965no change
7 Aug 2026, 12:5821,965first reading

Engagement

205 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 31 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.613%
avg views ÷ 22,088 subscribers
Avg views / post
135
205 posts measured
Reaction rate
3.65%
reactions ÷ views · ER floor
Posts in window
205
of 205 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. It is computed over the 199 of 205 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 August 2026
Posts held205 (7 August 202613 August 2026)
Views total27,770
Reactions total991
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 12:35 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
1,550
Videos
98
Links
64

Lifetime counters from Telegram’s own channel header, read 13 August 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
2m 11s
Average length
1m 06s

Measured directly from 2 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

991 reactions across 198 posts, in 6 distinct kinds. The most used accounts for 89.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍88789.5%
717.16%
🤩272.72%
❤‍🔥40.404%
👏10.101%
😱10.101%

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

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

13 Aug 2026, 12:34 UTC3 views0 reactionsread 13 August 2026
Photo

💰 转账给你 31.86 U 请在24小时内领取

Signed 辛巴

13 Aug 2026, 12:10 UTC10 views4 reactionsread 13 August 2026
Photo

想当恶魔代理的进这个群里,找小欧或者不名人,审核过了之后会拉你们进代理群🤫

👍4

Signed 不名人 Unknown person

13 Aug 2026, 11:49 UTC61 views4 reactionsread 13 August 2026
Photo

Photo, posted without a caption

👍31

Signed 南诗

13 Aug 2026, 11:24 UTC67 views2 reactionsread 13 August 2026
File

🔤🔤🔤🔤户籍猎手已公益 全网独一家 ⬇️手机号定位 ⬇️支付宝码反 ⬇️电百 联通 移动反 ❄️补齐身份证/手机号 ❄️个人大头 ❄️真/假地址 🛡手机号反姓名 🛡全国常用号 🛡v反/Q反三件套 🖥刑侦全户 🖥短信轰炸 📱无违规永久思路 🛰️无违规概率永久思路 🖥新增几个功能:ai脱换衣,破解梯子大全,酒店摄像直播,照片人脸扫描,精准模糊猎魔... 点我进入频道获取卡密 点我进入频道获取卡密

👍2

Signed 频道主全网收管理@oouo888

13 Aug 2026, 09:28 UTC144 views7 reactionsread 13 August 2026
Photo

这把有个同行比我还猛,趁他开车把他打了,恶魔nb哈

👍61

Signed 南诗

13 Aug 2026, 09:21 UTC51 views5 reactionsread 13 August 2026

在家没有去打工的,在家闲着也是闲着 不如在线上赚点生活费,没有门槛欢迎来赚钱联系 @mili13148

👍41

Signed 米粒 客服『秒结战神』

13 Aug 2026, 08:40 UTC176 views8 reactionsread 13 August 2026
Photo

Photo, posted without a caption

👍8

Signed 南诗

13 Aug 2026, 03:28 UTC67 views9 reactionsread 13 August 2026

点我下载obb 点我下载obb 点我下载obb 点我下载obb 点我下载obb 点我下载obb

👍9

Signed 南诗

12 Aug 2026, 23:48 UTC12 views1 reactionsread 13 August 2026
Photo

💰 转账给你 31.86 U 请在24小时内领取

👍1

Signed 辛巴

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

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

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

“恶魔直装主频道[冲23K]” (@SNKNB), 22,088 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SNKNB.

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.