🔺🔺新增诈骗犯 请谨慎交易🔺🔺 骗子的昵称:小淇 骗子用户名:@Rovoyl 苹果直达链接:tg://user?id=8905847576 安卓直达链接:tg://openmessage?user_id=8905847576 其他联系方式: 群组频道链接:https://t.me/xiao_i5 被骗的总金额 :10u 说明被骗过程 :10u都⭕️我没话说,消息已读不回,搁大群里库库发信息,同行避雷吧 诈骗犯另外一个号 @TG_x_Q 公示人:他爹 曝光联系: @tbxyh

Channel
TBX查档宇宙|防骗手册|反诈商家曝光
@tbxfp
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
10,823subscribers
-2,792 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003932372300 |
|---|---|
| Type | Channel |
| Username | @tbxfp |
| Created | Between 1 April 2026 and 15 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/tbxfp |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 09:17 | 10,823 | -79 |
| 16 Sept 2026, 01:39 | 10,902 | -265 |
| 14 Sept 2026, 06:14 | 11,167 | -213 |
| 12 Sept 2026, 11:37 | 11,380 | -104 |
| 10 Sept 2026, 08:20 | 11,484 | -29 |
| 7 Sept 2026, 02:37 | 11,513 | -45 |
| 4 Sept 2026, 08:37 | 11,558 | -21 |
| 2 Sept 2026, 20:38 | 11,579 | -29 |
| 1 Sept 2026, 15:55 | 11,608 | -23 |
| 31 Aug 2026, 17:44 | 11,631 | -34 |
| 30 Aug 2026, 19:17 | 11,665 | -200 |
| 29 Aug 2026, 20:18 | 11,865 | -142 |
| 28 Aug 2026, 21:36 | 12,007 | -19 |
| 27 Aug 2026, 22:45 | 12,026 | -3 |
| 27 Aug 2026, 00:18 | 12,029 | -53 |
| 26 Aug 2026, 01:04 | 12,082 | -32 |
| 25 Aug 2026, 04:21 | 12,114 | -7 |
| 23 Aug 2026, 23:47 | 12,121 | -15 |
| 22 Aug 2026, 06:15 | 12,136 | -12 |
| 20 Aug 2026, 20:33 | 12,148 | first reading |
Engagement
56 posts held, back to 15 July 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 46 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.182%
- avg views ÷ 10,823 subscribers
- Avg views / post
- 19.7
- 19 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 19
- of 56 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.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 56 (15 July 2026 – 2 September 2026) |
| Views total | 375 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 01:32 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.
What this channel posts
- Video runtime
- 7m 03s
- Average length
- 28s
Measured directly from 15 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.
Reaction mix
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.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 1 of the 56 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 56 most recent posts we hold, published 15 July 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.
Recent posts
#频道互推 #相似推荐 ------------------------------ 📢 【丰田】社工库开户开盒查档查人查车 📢 👑叮叮查档案源头.查档 开户 📢 Alway业务频道 📢 大头四方实卡接马⚠ 📢 【熊猫】bc数据/教育/棋牌/六合/全行业数据 📢 ws群发【WhatsApp群发】ws打粉、引流 📢 手机卡电销卡 📢 大牛抖音号-抖音【批发】 📢 三角洲12306内部/c内部官方通知频道 📢 官方888租售飞机号会员能量礼物NFT ------------------------------ ☁️ 互推入口:@sosoo
🔺🔺新增诈骗犯 请谨慎交易🔺🔺 骗子的昵称: 陈冠希 骗子用户名:@TTVVCCC 苹果直达链接:tg://user?id= 安卓直达链接:tg://openmessage?user_id= 其他联系方式:8202267443 群组频道链接: 被骗的总金额 :71u 说明被骗过程 :不读消息 不结账 公示人:@QZqiaozhi01 曝光联系: @tbxyh
⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ TBX宇宙是一个以信任为核心的交易保障平台 核心宗旨: 让你不再受骗·放心查档 ---------------------------------------------- 🟡平台十大核心功能 🆕 商家报备保证金背书,交易更有保障 🆕 自由交易灵活高效,透明安全 🆕 快速搜索,精准定位你需要的内容和服务 🆕 精选认证商家,资质一目了然 🆕 供需信息自由发布,快速精准匹配 🆕 你的专属钱包,资金流转更便捷 🆕 分享名片,轻松开启每一笔交易 🆕 收录申请,打开你的曝光入口 🆕 抢占关键词广告位,精准触达目标客户 🆕 邀请好友注册,坐享二级佣金收益 🔴🔴机器人入口 @tbxcdbot ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️
#频道互推 #相似推荐 ------------------------------ 📢 【永盛免费社工库】查档查档/开盒开户 📢 三角洲威龙数据号【三角洲0.1数据号】 📢 灰白通知频道【持续送卡】 📢 三角粥《柠檬内部》官方频道 📢 【老A口粮】越代🇻🇳走私香烟 📢 全球海外注册卡流量卡邮寄 📢 WS实卡接码【绮梦号商】 📢 短信通道 短信群发 106通道 国内短信 📢 海外账户源头批发通知 📢 MAXSMS双向短信官方唯一频道 ------------------------------ ☁️ 互推入口:@SosoCnBot
#频道互推 #相似推荐 ------------------------------ 📢 【丰田】社工库开户开盒查档查人查车 📢 👑叮叮查档案源头.查档 开户 📢 Alway业务频道 📢 大头四方实卡接马⚠ 📢 【熊猫】bc数据/教育/棋牌/六合/全行业数据 📢 ws群发【WhatsApp群发】ws打粉、引流 📢 手机卡电销卡 📢 大牛抖音号-抖音【批发】 📢 Telegram、Google各种外国号皆可詢問 📢 FB飞毛腿出海 【FB|批发】-大小黑号-IG-TK-领 ------------------------------ ☁️ 互推入口:@soso
🔺🔺新增诈骗犯 请谨慎交易🔺🔺 骗子的昵称:慈 支三机器人 骗子用户名:@cide03 苹果直达链接:tg://user?id=7030636873 安卓直达链接:tg://openmessage?user_id=7030636873 其他联系方式:7030636873 被骗的总金额 :一个批三 说明被骗过程 :说什么给他批三就给机器人永久授权给了他以后就说什么要泛滥后面又把永久推到30天然后15天口声声说是垃圾批三自己玩的挺开心的 公示人: @Naive776 曝光联系: @tbxyh
🔺🔺新增诈骗犯 请谨慎交易🔺🔺 骗子的昵称:记得记得 骗子用户名:@dqdq101957 苹果直达链接:tg://user?id= 安卓直达链接:tg://openmessage?user_id= 其他联系方式: 群组频道链接:可以不填写 被骗的总金额 :10 说明被骗过程 :装死不结账 曝光联系: @tbxyh
#频道互推 #相似推荐 ------------------------------ 📢 【永盛免费社工库】查档查档/开盒开户 📢 三角粥《柠檬内部》官方频道 📢 【老A口粮】越代🇻🇳走私香烟 📢 全球海外注册卡流量卡邮寄 📢 WS实卡接码【绮梦号商】 📢 短信通道 短信群发 106通道 国内短信 📢 小白灰产赚钱项目百科知识 📢 代认证/备案域名加急/注册营业执照/ 📢 海外账户源头批发通知 📢 大鲨鱼权威查档|@bgshark ------------------------------ ☁️ 互推入口:@soso
#频道互推 #相似推荐 ------------------------------ 📢 【丰田】社工库开户开盒查档查人查车 📢 Alway业务频道 📢 大头四方实卡接马⚠ 📢 【熊猫】bc数据/教育/棋牌/六合/全行业数据 📢 ws群发【WhatsApp群发】ws打粉、引流 📢 手机卡电销卡 📢 大牛抖音号-抖音【批发】 📢 三角洲威龙数据号【三角洲0.1数据号】 📢 微信抖音快手小红书 📢 🥇🥇🥇电报会员/频道/在线/点赞/关注 ------------------------------ ☁️ 互推入口:@SosoCnBot
#频道互推 #相似推荐 ------------------------------ 📢 【永盛免费社工库】查档查档/开盒开户 📢 三角粥《柠檬内部》官方频道 📢 【老A口粮】越代🇻🇳走私香烟 📢 全球海外注册卡流量卡邮寄 📢 WS实卡接码【绮梦号商】 📢 短信通道 短信群发 106通道 国内短信 📢 小白灰产赚钱项目百科知识 📢 代认证/备案域名加急/注册营业执照/ 📢 大鲨鱼权威查档|@bgshark 📢 Telegram、Google各种外国号皆可詢問 ------------------------------ ☁️ 互推入口:@sooo
🔺🔺新增诈骗犯 请谨慎交易🔺🔺 骗子昵称:知名 主页支付宝名字机器人 骗子用户名:@cpaav 苹果直达链接:6410179797 安卓直达链接: 其他联系方式: 群组频道链接: 被骗的总金额 :50u 说明被骗过程 :11号找我推荐机器人,今天机器人没反应了一去问他,喊我继续打钱,脑残一个, 曝光联系: @tbxyh
Showing the 12 most recent of 56 posts we hold for @tbxfp. 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
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.
Mentions
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.
@tbxooo · 11312 posts大鲨鱼权威查档|@bgshark
@bgshark03 · 18,30111 posts独断万古-防失联
@duduanwangu111 · 5,41211 posts后羿团队出品
@houyituanduichupin · 1,64811 posts上帝之眼查档专家
@Jdjdbdnno · 39,04511 posts名下号查档信修源头通知频道
@swyt110 · 1,31411 posts上帝之眼@oooww
@tbxggg · 53,10311 postsSOSO搜搜
@sooo · 541,11510 posts万豪查档业务通知频道
@wanhao9999999 · 42210 posts巨量星核|网红曝光大事件
@tbxaaa · 8,5669 postsTBX查档宇宙|核心商户资源群
@tbxcddb · 10,5839 postsTBX查档宇宙|官方群@tbxdq
@tbxdq · 14,7179 postsTBX查档宇宙|认证商家龙虎榜@tbxlh
@tbxlh · 759 postsTBX查档宇宙|B2B资源供应社区
@tbxsss · 8,5299 posts永盛天眼官方社工库通知
@yssgktyc · 13,7734 postsTBX查档宇宙|官方频道@tbxcd
@tbxcd · 14,7783 postsSOSO搜搜🔞
@SosoCnBot · 212,7442 posts大富大贵你花生哥
@huidannb666 · 981 post永恒 API
@newyanchannel · 2,6081 postSOSO搜搜
@sosoo · 452,0601 post别离花专业查档🧿
@wenquanmiao · 1141 post小淇的朋友圈
@xiao_i5 · 2011 post
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@tbxfp named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 3 posts, 16 August 2026 – 21 August 2026 · confirmed gone 11 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“TBX查档宇宙|防骗手册|反诈商家曝光” (@tbxfp), 10,823 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/tbxfp.
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.