内部端为云更新 点击软件里面的更新规则即可
👍2

Channel
@SCNBDN
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry
20,513subscribers
+5,887 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002378022755 |
|---|---|
| Type | Channel |
| Username | @SCNBDN |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 October 2026 |
| Measurements held | 40 |
| Confirmed unchanged | 1 time, most recently 18 October 2026 |
| On Telegram | t.me/SCNBDN |
Software piracy — 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 71% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Oct 2026, 00:20 | 20,513 | -193 |
| 17 Oct 2026, 00:05 | 20,706 | -266 |
| 15 Oct 2026, 23:47 | 20,972 | +9,209 |
| 15 Oct 2026, 01:46 | 11,763 | -174 |
| 13 Oct 2026, 23:09 | 11,937 | -1,210 |
| 10 Oct 2026, 22:17 | 13,147 | +717 |
| 6 Oct 2026, 18:22 | 12,430 | -1,691 |
| 1 Oct 2026, 19:37 | 14,121 | -2,319 |
| 18 Sept 2026, 10:37 | 16,440 | -469 |
| 16 Sept 2026, 04:39 | 16,909 | -330 |
| 14 Sept 2026, 14:00 | 17,239 | -251 |
| 13 Sept 2026, 01:36 | 17,490 | -355 |
| 11 Sept 2026, 05:38 | 17,845 | -821 |
| 8 Sept 2026, 11:00 | 18,666 | +479 |
| 5 Sept 2026, 06:37 | 18,187 | -274 |
| 3 Sept 2026, 14:17 | 18,461 | -78 |
| 2 Sept 2026, 08:25 | 18,539 | -102 |
| 1 Sept 2026, 08:15 | 18,641 | -60 |
| 31 Aug 2026, 08:44 | 18,701 | -19 |
| 30 Aug 2026, 12:04 | 18,720 | first reading |
64 posts held, back to 6 April 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 54 pages 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 64 posts for this entry, the most recent from 2 September 2026. An engagement rate over an empty window would be a number about nothing.
437 reactions across 50 posts, in 14 distinct kinds. The most used accounts for 40.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 176 | 40.3% | |
| ❤ | 152 | 34.8% | |
| 🥰 | 34 | 7.78% | |
| 👎 | 20 | 4.58% | |
| 🔥 | 19 | 4.35% | |
| 🤔 | 14 | 3.20% | |
| 👏 | 9 | 2.06% | |
| 😱 | 3 | 0.686% | |
| 🍌 | 2 | 0.458% | |
| 🐳 | 2 | 0.458% | |
| 💩 | 2 | 0.458% | |
| 😁 | 2 | 0.458% | |
| 🤩 | 1 | 0.229% | |
| 🤮 | 1 | 0.229% |
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 52 of the 64 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 437 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 64 most recent posts we hold, published 6 April 2026 to 2 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.
内部端为云更新 点击软件里面的更新规则即可
👍2
神楚公益端口 更新时间9.3日 账号密码 123 免白全火连打 可防全火半火直装文件 不防特征功能以及文件美化 官方导航 神楚.xyz 反馈联系 @shechu1314
🥰2👍1
神楚所有项目先暂停使用 等更新
👍3❤2
⚠️神楚直装 img版本 ✅内核级别掩体漏打 ✅适配市面所有机型 ✅修复三方问题 📣暂时公益卡密随便输入 👉自行配拦截或者全防使用 🎉有问题联系 @shechu1314
👍8❤2🔥1
准备出个直装了😋
👍25🤔8❤1🥰1
⚠️神楚公益全防 ✅防全火 ✅防半火 ✅防追踪 ✅防纯C ‼️禁止使用特征功能 🍉卡密随便输入 🎉反馈联系 @shechu1314 📣数据号购买地址 https://www.hl623.cn/shop/scsjh
👍8❤1🔥1
Signed 神の最终章
公益端口服务器带宽满了 一会升级一下
👍7❤1🥰1
Signed 神の最终章
Sticker, posted without a caption
👍4🥰2
要不要出一个全防
The shares total 105%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
👍8🥰2❤1
⚠️神楚自动注入1.6版本 ✅优化卡顿问题 ✅优化整体UI ✅优化注入文件功能 ✅新增无痕模式 建议搭配神楚端口使用 👉完全公益无需卡密 🎉反馈联系 @shechu1314 📱直登号购买地址 https://www.hl623.cn/shop/scsjh
👍10❤4🥰3🐳2😱1
⚠️神楚拦截1.1版本 ✅独家UI界面 ✅11000条拦截规则 ✅采用独家全火规则 ✅防文件 ✅防直装 ✅防注入 ✅防全火 ✅防半火 ✅防追踪 ‼️禁止使用特征的辅助‼️ 公益卡密 SCDLWARG 👉项目官网 神楚.xyz 🎉反馈联系 @shechu1314
❤10👍3🍌2👏1🔥1🤩1
庆祝频道人数14k 给大家发一个红包
👍3
Signed 实名 八弟
Showing the 12 most recent of 64 posts we hold for @SCNBDN. 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.
@SCNBDN edited 4 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.
The 5 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
要不要出一个全防
The shares total 105%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
要不要出一个拦截
Shares as published. No per-option vote count is published by Telegram, so none is shown.
和平上强检了吗
Shares as published. No per-option vote count is published by Telegram, so none is shown.
你们觉得端口现在还有什么需要更新的地方吗
Shares as published. No per-option vote count is published by Telegram, so none is shown.
✅你们觉得神楚公益端口稳不稳定
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 64 most recent posts we hold, published 6 April 2026 to 2 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“神楚项目通知频道” (@SCNBDN), 20,513 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/SCNBDN.
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.