Telegram RegisterThe public register of Telegram
Telegram profile photo for 三角洲《柚子内部》官方通知群

Channel

三角洲《柚子内部》官方通知群

@NMNBSS

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

3,920subscribers

+399 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-1004359662149
TypeChannel
Username@NMNBSS
CreatedBetween 1 June 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 September 2026
Last confirmed live4 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/NMNBSS

Topic

Giveaways & airdrops — 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 68% 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

3,5214,0223,771.510 September 2026 — 3,521 subscribers10 September 2026 — 3,521 subscribers12 September 2026 — 3,822 subscribers15 September 2026 — 4,022 subscribers25 September 2026 — 4,000 subscribers4 October 2026 — 3,920 subscribers3,92010 September 20264 October 2026
6 measurements spanning 24 days, net +399. 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 3,446–4,097 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 18:183,920-80
25 Sept 2026, 07:164,000-22
15 Sept 2026, 18:004,022+200
12 Sept 2026, 07:183,822+301
10 Sept 2026, 18:223,521no change
10 Sept 2026, 17:473,521first reading

Engagement

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

ERR · 30 days
7.63%
avg views ÷ 3,920 subscribers
Avg views / post
299
9 posts measured
Reaction rate
1.15%
reactions ÷ views · ER floor
Posts in window
9
of 17 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 8 of 9 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 10 September 2026
Posts held17 (6 August 2026 – 10 September 2026)
Views total2,692
Reactions total30
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Sept 2026, 18:22 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

438 reactions across 16 posts, in 13 distinct kinds. The most used accounts for 48.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎21448.9%
🖕11426.0%
💩4410.0%
👍245.48%
❤122.74%
🤣92.05%
🤔71.60%
👏40.913%
😁30.685%
🌚20.457%
👾20.457%
🤡20.457%
🤬10.228%

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

Measured over the 17 most recent posts we hold, published 6 August 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

10 Sept 2026, 18:11 UTC57 views1 reactionsread 10 September 2026
Photo

免费500张福利卡 自行取卡!! (https://t.me/NMNBSS/2685 ) (https://t.me/NMNBSS/2685 ) (https://t.me/NMNBSS/2685 ) 拿包联系客服! @NMNBAA 🛫官方频道:https://t.me/NMNBSS

👍1

10 Sept 2026, 18:03 UTC70 views1 reactionsread 10 September 2026

S8CszGl2dRHg GarfdeIc661F 03EzccJHOTu1 4y3stvOHzhyG 0gdgxpNERHir tGtuYrJvkLTk EaoqhkTT3wkb 5iowHb6k82YR lTurfXAIq7br 8rqpNLevXc0s qR9A9wcLq0Ee aXUvjC1Orgfq 62i4rn81ZRqW ZjMNcIGJyoRW rUVbudXuqC4B hRfzHqn48AKC 3ePdPGX8nuuG iBB3x3vkdkyT FTrmt3V6vcOV ZycNiUO3CvsN zAd5knZoWgoK ZkGorQ6mmcwH 9iEsoNQhmk4O G8s0Q9nFlbbp vWCfYJd2c2cF 4TTWWiYw8DEG hyxDRMCd3VwB Jdi3rtN0nQOw 9alBCpngdseY nvTCt4ICUX1O 4RdNg79CJdY9 IzSwnTkKzjxM 1GGV…

👍1

10 Sept 2026, 17:30 UTC80 viewsread 10 September 2026

来几个加密的人 送纯算法柠檬一天 来人测试效果 纯算法 !!随便玩大号小号都可以!! 唯一客服 @NMNBAA

10 Sept 2026, 14:32 UTC232 views1 reactionsread 10 September 2026

柠檬此次更新增加漏打变色!!全网唯一首发纯算法!!不动任何内存!!和谐=无效果不会十年

👍1

10 Sept 2026, 13:55 UTC268 views1 reactionsread 10 September 2026

还没弄好 稍等一会发布!!解决下小bug 一会在回私聊

👍1

10 Sept 2026, 13:48 UTC683 views1 reactionsread 10 September 2026
Photo

❗️❗️❗️❗️❗️ 🌐三角洲《柠檬漏打变色》 支持新赛季 👍绘制:骨骼-方框-距离-血量-头甲-角色-物资透视-物资价值 👍自瞄:纯模拟人手Ai梓喵,不动任何内存 👍驱动:独家自研驱动(稳定奔放) 👍解密:采用纯模拟算法不动任何内存 👍支持服务器:国服 👍支持内核版本:5.1-5.15-6.12 6.6 6.12.58等等内核 🛫官方频道:https://t.me/NMNBSS 解密:采用纯模拟算法不动任何内存 ✅柠檬内核无任何代理✅ 🔝每天发放30名天/周名额🔝 🔝每天发放50名额测试卡名额🔝 无任何代理,官方频道只此此一个,长期项目!! 建议护航打手开卡!!其他的不建议!! 认准唯一官方频道:https://t.me/NMNBSS 唯一客服 @NMNBAA 双向机器人 @nmnbssbot 稍后送出500张福利卡!! 稍后送出500张福利卡!! 稍后送出500张福利卡!!

👍1

10 Sept 2026, 05:41 UTC537 views7 reactionsread 10 September 2026

之前批卡的代理找我补卡换卡 !!

👍4👎2❤1

10 Sept 2026, 05:41 UTC537 views16 reactionsread 10 September 2026

回归了 稍后送300张12小时卡!!

👍9💩7

7 Aug 2026, 10:54 UTC≈3,120 views180 reactionsread 10 September 2026

个别没效果的 等解决了送1-2天时间 只要提过天卡的 8.6日12点以后提过卡的 都可以 白嫖2天时间!!

🖕107💩37👎13🤣9🤔6❤3👾2🤡2

7 Aug 2026, 05:28 UTC≈3,150 views59 reactionsread 10 September 2026

出现个别没效果的 正在解决中!!!

👎48🖕7❤2👍1🤔1

7 Aug 2026, 05:28 UTC≈3,150 views40 reactionsread 10 September 2026

出现个别没效果的 正在解决中!!!

👎38👍2

Showing the 12 most recent of 17 posts we hold for @NMNBSS. 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 1 registered channel — 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 4 October 2026 — this entry's latest reading, not the date you are reading this.

“三角洲《柚子内部》官方通知群” (@NMNBSS), 3,920 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/NMNBSS.

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.