🥰今天敲了三万字,累了💤!兄弟们早点休息😴
❤4🫡1

Channel
@SMBL168
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
17,810subscribers
-189 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002218399052 |
|---|---|
| Type | Channel |
| Usernames | @i3boss @il3_ll @l888884 @laobtc @ncnnnnnnnn @nnnnnnvnnn @SMBL168 @smblc |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 70 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/SMBL168 |
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 10 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 12:37 | 17,810 | no change |
| 19 Sept 2026, 17:19 | 17,810 | -31 |
| 18 Sept 2026, 12:55 | 17,841 | +21 |
| 18 Sept 2026, 06:41 | 17,820 | +37 |
| 18 Sept 2026, 02:59 | 17,783 | +4 |
| 17 Sept 2026, 21:21 | 17,779 | no change |
| 17 Sept 2026, 21:16 | 17,779 | +13 |
| 17 Sept 2026, 12:20 | 17,766 | -3 |
| 17 Sept 2026, 05:20 | 17,769 | -1 |
| 16 Sept 2026, 02:57 | 17,770 | -3 |
| 15 Sept 2026, 23:22 | 17,773 | -3 |
| 15 Sept 2026, 21:56 | 17,776 | no change |
| 15 Sept 2026, 20:37 | 17,776 | +1 |
| 15 Sept 2026, 16:00 | 17,775 | +5 |
| 15 Sept 2026, 10:19 | 17,770 | +3 |
| 15 Sept 2026, 07:41 | 17,767 | +2 |
| 15 Sept 2026, 03:40 | 17,765 | -13 |
| 14 Sept 2026, 07:40 | 17,778 | +6 |
| 14 Sept 2026, 06:19 | 17,772 | no change |
| 14 Sept 2026, 06:17 | 17,772 | first reading |
266 posts held, back to 17 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 45 pages of Telegram’s post history, 20 posts per page.
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 74 of 133 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 September 2026 |
|---|---|
| Posts held | 266 (17 August 2026 – 12 September 2026) |
| Views total | 175,577 |
| Reactions total | 705 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Sept 2026, 15: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.
Measured directly from 10 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.
1,582 reactions across 163 posts, in 39 distinct kinds. The most used accounts for 37.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 595 | 37.6% | |
| 💩 | 310 | 19.6% | |
| ❤ | 231 | 14.6% | |
| 👏 | 108 | 6.83% | |
| 🤡 | 105 | 6.64% | |
| 🔥 | 53 | 3.35% | |
| 🌚 | 28 | 1.77% | |
| 🎉 | 18 | 1.14% | |
| 👌 | 17 | 1.07% | |
| 👎 | 12 | 0.759% | |
| 🍾 | 10 | 0.632% | |
| 💯 | 10 | 0.632% | |
| 🖕 | 10 | 0.632% | |
| 😁 | 7 | 0.442% | |
| 🤔 | 7 | 0.442% | |
| 🏆 | 6 | 0.379% | |
| 😭 | 6 | 0.379% | |
| 🤷 | 6 | 0.379% | |
| 🐳 | 5 | 0.316% | |
| 😈 | 5 | 0.316% | |
| 19 further kinds | 33 | 2.09% |
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 174 of the 266 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 1,582 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 266 most recent posts we hold, published 17 August 2026 to 12 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.
🥰今天敲了三万字,累了💤!兄弟们早点休息😴
❤4🫡1
🤬方法教了,盘方给你们找了,要是还赚不到钱那就要好好审视一下自己了 还有盘口的客户,每一波都会有只跟票不开户的客户,懂得都懂,利用起来变现也是很爽的
👍6🤡2
🤩神秘部落担保项目 港股接盘,14号开始进场暂定做到18号,刚合完股的一只票,没限制任何券商都可以交易! 记者同行勿扰! @LJL168888
🤩今天到这里真的结束了,有什么困难都可以发在评论区 空闲时间我都会讲解一下
❤️🔥今天打了这么多字,有点梦回当年了! 如果一天没有打3万字,还做什么业务?
🤡6💩4🖕3
3:前期基本聊一聊股票,然后切到生活,毕竟股票知识不专业,生活话题比较简单,双方认识,成为朋友 4:重点是在交易日懂吗,你以前做大区,助理号是不是在交易日跟客户比较火热,那么用朋友来聊,就是互相分享,如果你不知道和对方聊什么票,那么打开股市同学会,每天都有大V推票,就和同花顺论坛一样 5:根据盘方时间去计算客户的维护周期,例如这月18号有票可以买,那么今天我认识了客户,经过了解,成为朋友,下周交易日就可以互相分享票,适当的P图嗮一下自己的战绩,这些论坛里面的都有 6:双方喂票的过程中就可以铺垫一下,最近一个朋友买港股赚多少钱,(这是一个例子,不是固定引导话题)然后和客户浅聊一下,第二个交易日随便找一个港股暴涨的,说自己听朋友的买了,可以配上图片,客户会让你一起分享,因为是正规购买,戒心不会那么高 总体思路就是这样,当然了,人有千样,要用不同的话术切入,自己好好思考吧!
❤3👍2
👍今天直接口述吧!接盘切课的话术和思路 1:首先我们包装了一个号,男女都可以,看自己擅长什么,可以包装六七个号一起,就和三方一样的,人物背景,照片视频都搞好 2:开始地推,例如我们在评论区看到一个股民用户,说买了什么,最近亏了,然后进行私信交流,私信打招呼话术随机的,可以说自己也买了,引起共鸣然后聊下去,这个可以搬照频道里发的精聊7天步骤,但是不是让你真精聊他,是让你有个框架,有话题聊
💩4👍2
👍关于接盘这个粉的问题我在说一下 例如台湾,在FB上面有很多台湾反诈联盟,下面全部是真实用户,还有股市同学会,雅虎,渠道太多了 重要的是执行,不是犹豫,犹豫就会败北
Signed 神秘部落导航站-网络日记📓
👍👍下课下课! 需要什么配套的可以看下公示系统,都有标注合作方,解决大家的实际需求 上号可以找柔妹,美工台子卷毛,通道换汇接盘开会员TRX兑换找蓝精灵,剧本配套小米,租台子恒升 今天就到这里!没事多思考一下吧!
Signed 神秘部落导航站-网络日记📓
你不赌不要劝我不赌,它一定会出的 🏡金运国际娱乐: jygj888.top (PG电子好打) 👍 双狮官方网址: ssgj55.cc (大水爆分中) 💸宝格丽娱乐城: bgljxf.vip (火热爆分中)
❤2
Signed 认准ID @jxhbb 江小壶天 借钱拉黑
👍如果这些你都不想做,那么就只能用出最快速的了,点击置顶🔝金运,双狮平台 怒冲100,也许会变成1万,百倍产出 但是个人感觉还是要有固定搞钱的能力,所以请加油吧!
🌚1
👍再说到韩国飞机协议,最近也是半死不活的,前段时间可以拉50人,个人感觉没什么意义 现在的环境要求就一个字:快 打粉周期一定要控制好,否则很容易全军覆没
Showing the 12 most recent of 266 posts we hold for @SMBL168. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
兄弟们认为哪里的大区好做?
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 266 most recent posts we hold, published 17 August 2026 to 12 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 3 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“神秘部落研习室” (@SMBL168), 17,810 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/SMBL168.
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.