Channel
@fawubusgk
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,420subscribers
+19 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003310966538 |
|---|---|
| Type | Channel |
| Username | @fawubusgk |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/fawubusgk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 09:18 | 2,420 | +14 |
| 12 Aug 2026, 01:42 | 2,406 | +3 |
| 9 Aug 2026, 10:51 | 2,403 | +2 |
| 9 Aug 2026, 01:15 | 2,401 | first reading |
19 posts held, back to 22 June 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 pageof 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 5 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 19 (22 June 2026 – 8 August 2026) |
| Views total | 3,393 |
| Reactions total | 10 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 01:15 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.
55 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 56.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 31 | 56.4% | |
| 👍 | 20 | 36.4% | |
| 🥰 | 3 | 5.45% | |
| 😱 | 1 | 1.82% |
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 13 of the 19 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 55reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 22 June 2026 to 8 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.
#频道互推 #相似推荐 ------------------------------ 📢 全球海外注册卡流量卡邮寄 📢 【丰田】社工库开户开盒查档查人查车 📢 【老A口粮】越代🇻🇳走私香烟 📢 短信通道 短信群发 106通道 国内短信 📢 大牛抖音号-抖音【批发】 📢 【熊猫】bc数据/教育/棋牌/六合/全行业数据 📢 三角粥《柠檬内核/789内部/X5内部》官方频道 📢 抖音兼职🅥灰产赚钱项目 📢 出售🔥国内🔥一手 私人 微信🍉（微信号商小鬼） 📢 老虎地推盖章收粉俱乐部 ------------------------------ ☁️ 互推入口：@sooo
频道适合看内容，群组更适合继续交流。 SOSO 可以直接找热门群组，也能按关键词搜同类圈子。 先打开看看当前推荐。
抱歉，朋友们，最近忙着打牌，没来得及更新。😁 马上跟新，继续做生产队的驴 内容导航 😘
👍4
看图找漏斗系列~ 请看看图片有几点不对？🙈 1.BC 二道料？ 好新奇的词汇 2.登录微信搭建收款通道？ 3.洗钱用微信洗到支付宝完成？ 请朋友们找出更多的bug问题~ 跳转骗局大合集 阅读更多😘
👍1😱1
江湖义士之小熊供需频道 寻查档频道主置换广告合作： 1，必须是查档社工类频道； 2，必须是真人频道； 3，满300真人以上即可置换； 4，小熊供需频道目前3500人； 5，小熊供需全是真人，全是之前狗狗个户机器人、小熊全系列机器人的充值客户。 小熊供需频道：@xiaoxiong115 置换联系客服：@zxcfggy 再热爱代码也需要吃饭， 再热衷提交接口也需要银子， 特此插播一条~为技术人才谋福利 后续多多投稿技术方向动态
断层设计与风险规避—— 插播篇 接上文，请看这里回顾下，为什么说不要用这两个钱包； 虽然钱包app是匿名的，但app会记录： 1.设备信息 2.登录IP 3.位置轨迹 这些信息还不够敏感吗？ 比特派夸张到一个基层管所的涵件都配合出信息了~! 还不恐怖吗？ imToken据传同杭州的某些部门有某些神秘合作的！ 还有最近很火的一款硬件钱包：OneKey 去看看他的资方（+86的，管理团队+86的！） 阅读更多 😘
❤2👍1🥰1
计算公式（接料、放料） ①、点位计算： 【1-(实时汇率➗交易汇率)】*100=点位 如：实时汇率：7 交易汇率：8.5 【1-（7➗8.5）*100】=18点位 ②、汇率计算： 1-『点位➗100』=X 实时汇率➗X=汇率 如：点位：17 实时汇率：7 1-（17➗100）=0.83。 7➗0.83=8.5汇率 好多小伙伴计算不明白，参照此公式就好。 看料性点这里 阅读更多 😘
Posted without readable text
Posted without readable text
不建议开着节点访问抖音、哔哩哔哩、小红书，进行装逼行为。 其他用户看到你的 IP 不同，可能会觉得你很酷炫，但是平台并不会只看你的 IP。 平台可以通过手机环境、定位权限、附近 Wi-Fi、基站、SIM 卡和运营商信息、设备信息、WebRTC/STUN 请求、收货地址等各种手段，比较轻松地判断你的真实位置，或者把你的不同账号和设备关联起来。 需要注意的是，WebRTC 一般主要是泄露本地 IP、网络信息，或者暴露你正在使用代理，并不一定能直接绕过节点查到你的真实公网 IP。但是结合设备、定位、基站、账号和历史登录记录，平台还是有很多办法判断你的真实情况。 比如，美团这类软件一般都会维护自己的 IP 和位置数据库。如果你挂着节点打开美团，就有可能把节点 IP 和你的收餐地址、定位、基站、设备信息绑定或关联起来。 虽然单独看可能没什么大影响，但是这只是一个外卖软件能做到的事情，其他软件能做到的绝对不止这些。 搜狗输入法这…
👍5❤3
断层设计与风险规避—— 第二章：经营业态与断层取舍 前言：脱离业务属性空谈断层规避没有任何意义！口嗨误事儿，影响太多哇！ 业务属性和分工角度（上下游联系） 如果你的业务有线下环节，那实现绝对的断层毫无可能，上下游0口供一样会指认的； 应了那句话：酒桌全是兄弟情，口供全是兄弟名~🙊 举例说明，一起思考交流下 资金类：码/卡 回U 还是 实物车 现金车 还是 代还代缴呢？ 对应的逻辑不一样的； 纯线上的业务只需要考虑，上下游联系的渠道（结合信息流），资金穿透链路；此处暂扩展说经营逻辑，后续更新~ 有线下环节的从业朋友，需要考虑的就要多一些了，同下游的细节就非常多了，请逐项思考吧~ 服务类：拉皮条的、开盒查档；请考虑清楚的你的客群集中在哪里，外网内网？ 外网你同下游联系的工具是什么呢，资金上下游结算 内网你的客群 引流 等等环节，请想下~ 业务收入和成本角度（业务逻辑线） 两个角度： A业务的运行环节中，如果增加断层设计，对既…
❤4🥰2👍1
近期不下十个朋友私信说找项目被骗。 动动脑子好吧！ 无语死了，别私信了，每天太忙，事情很多，看到会回复的，频道尽量更新，去看看骗局大合集好吧，断层还没写完呢。
Showing the 12 most recent of 19 posts we hold for @fawubusgk. 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.
Citation-graph rank — 353,576 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“小白灰产赚钱项目百科知识” (@fawubusgk), 2,420 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/fawubusgk.
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.