Telegram RegisterThe public register of Telegram
Telegram profile photo for 白柠

Channel

白柠

@BNSTR

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

110subscribers

+33 since we began measuring on 23 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003372132657
TypeChannel
Username@BNSTR
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 August 2026
Last confirmed live11 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/BNSTR

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

7711093.523 August 2026 — 77 subscribers24 August 2026 — 77 subscribers1 September 2026 — 97 subscribers9 September 2026 — 102 subscribers17 September 2026 — 107 subscribers30 September 2026 — 108 subscribers11 October 2026 — 110 subscribers23 August 202611 October 2026
7 measurements spanning 50 days, net +33. 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 72–115 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 22:01110+2
30 Sept 2026, 19:21108+1
17 Sept 2026, 03:17107+5
9 Sept 2026, 13:20102+5
1 Sept 2026, 05:4797+20
24 Aug 2026, 14:1677no change
23 Aug 2026, 01:0077first reading

Engagement

20 posts held, back to 5 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.

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

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2100.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 2 of the 20 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

22 Aug 2026, 19:48 UTC12 views1 reactionsread 23 August 2026

内部项目2k+ 的解密游戏私钥,直接通过加密坐标算出真实坐标,完美解决目前udp解密1/3/7

👍1

22 Aug 2026, 16:39 UTC30 views1 reactionsread 23 August 2026

更新预告 三角洲算法解密,不是模拟不是内存

👍1

22 Aug 2026, 15:55 UTC≈1,010 viewsread 23 August 2026

⭐️白柠root内核开发中✅ ✅支持root写入手机底层Linux ✅超强隐藏性附着于system区 ✅分散式附着自瞄 读取 ✅system_ext system_dlkm ✔️可选择开启拦截云下发 ✔️拒绝十年✔️ ❤️❤️❤️❤️❤️❤️❤️ 认准白柠❤️ 点击我加入频道 点击我加入频道 点击我加入频道 👑支持游戏: 和平精英✔️ 三角洲✔️ PUBG✔️ 萤火突击✔️ cf✔️ 时空进化✔️

20 Aug 2026, 17:53 UTC98 viewsread 23 August 2026

Disclaimer 1. All programming resources, source codes, development tutorials and technical services provided here are for legal personal learning, legitimate commercial software development, academic research and technical practice only. ​ 2. We DO NOT accept, develop, sell or distribute any tools, scripts, websites or bots related to illegal gambling, online fraud, pornographic content, hacking, unauthorized data t…

20 Aug 2026, 17:41 UTC91 viewsread 23 August 2026

本人业务如下 1.网站前段开发 2.telegram机器人部署 3.c/c++ 开发 4.c++[imgui内核ui]开发 5.lua脚本ui开发 6.ai类业务 联系方式 @hb_nb 双向机器人 @ZQBN_bot ======================== 不合作诈骗 赌博 涉黄 核心开发 ======================== ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ My business is as follows 1. Website front-end development 2. telegram robot deployment 3.c/C + + development 4.c + + [IMG UI kernel UI] development 5. Lua script UI development 6.ai business Contact information @hb_Nb Bidirec…

18 Aug 2026, 18:07 UTC94 viewsread 23 August 2026

群聊指令 ws 查看余额 回复+ sy 金额 转账 回复+sy 金额 数量 红包 发送 yx 选择游戏 快三 上庄 庄家加金额 加庄 加余额 大 小 合 测试群https://t.me/wushenqb

Showing the 12 most recent of 20 posts we hold for @BNSTR. 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 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 11 October 2026 — this entry's latest reading, not the date you are reading this.

“白柠” (@BNSTR), 110 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/BNSTR.

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.