Channel
@hxsbl
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
11,058subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003218733885 |
|---|---|
| Type | Channel |
| Username | @hxsbl |
| Description | 投稿机器人： @menggetg_bot 唯一商务合作： @TGlangdao 唯一免费投稿： @hxsb1 ⚠️：建议联系机器人，优先回复机器人消息。投稿账号不谈商务！！！ 如果想了解有关在东南亚推推们的大事小情关注本频道准没错。注意，本频道只负责报道相关资讯，真假请自行分辨，如果需要删帖澄清需爆料者本人联系本频道负责人。最后祝福所有在东南亚打拼的推推们早日上岸！！！ #东南亚 #泰国 #缅甸 #金三角 #迪拜 #柬埔寨 |
| Created | Between 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 6 times, most recently 12 August 2026 |
| On Telegram | t.me/hxsbl |
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 57% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 4 other registered channels. They sit inside a group of 8 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @hxsbl/1900 · this entry7 Aug 2026, 06:14 UTC | @haixiashibao1/38907 Aug 2026, 06:17 UTC | 1.00 | 2 minutes |
| @hxsbl/1901 · this entry7 Aug 2026, 06:14 UTC | @haixiashibao1/38917 Aug 2026, 06:17 UTC | 1.00 | 2 minutes |
| @hxsbl/1905 · this entry7 Aug 2026, 06:14 UTC | @haixiashibao1/38957 Aug 2026, 06:17 UTC | 1.00 | 2 minutes |
| @hxsbl/1908 · this entry7 Aug 2026, 06:14 UTC | @haixiashibao1/38987 Aug 2026, 06:17 UTC | 1.00 | 2 minutes |
| @hxsbl/1910 · this entry7 Aug 2026, 06:14 UTC | @haixiashibao1/39007 Aug 2026, 06:17 UTC | 1.00 | 2 minutes |
| @hxsbl/1913 · this entry7 Aug 2026, 06:17 UTC | @haixiashibao1/39037 Aug 2026, 06:17 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @haixiashibao1 | 16 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | this entry (16–0) |
| @gtkx1 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 78 minutes | @gtkx1 (6–0) |
| @bxc888 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 1.9 hours | this entry (5–0) |
| @DNYXW008 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 1.9 hours | this entry (5–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 6 of the 6 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 26 comparable posts for this entry, running 7 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 8, the earliest publisher we hold is @gtkx1. That is a statement about our reading window, not a claim of authorship.
3.9 average views per post against 11,058 subscribers — an engagement rate of 0.035%. Across the 1,871 registered channels in the same cohort — 10,003–31,611 subscribers, posting mainly in Chinese — the middle half sit between 1.94% and 11.5%, with a median of 4.82%.
| Window | 30 days (13 July 2026 – 12 August 2026) |
|---|---|
| Posts measured | 58 of 58 published in the window (58 exact, 0 rounded by Telegram) |
| Views totalled | 228 |
| Mature posts only | 0.063% over 12 posts read at least 24h after publication |
| Subscribers | 11,058 measured 7 August 2026 |
| Cohort | b10000:zho · 1,871 channels · p10 0.566% · p25 1.94% · p50 4.82% · p75 11.5% · p90 24.9% |
| Position in cohort | 0.856th percentile · 1/143 the cohort median |
| Uncertainty | ±0.261% of the figure, from Telegram’s rounding |
| Post language | Chinese · 100.0%of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the keys clone_copy · clone_source · err_low, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 7 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 20:27 | 11,058 | no change |
| 7 Aug 2026, 09:01 | 11,058 | first reading |
58 posts held, back to 7 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 15 pagesof 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.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 58 (7 August 2026 – 8 August 2026) |
| Views total | 228 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 13:31 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.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 6 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.
👍👍👍👍专业：手机银行，电脑银行，微信支付宝的转账截图，银行到账短信 身份证 USDT... 等做图生成器，行走江湖必备神器，助力你业绩爆表🤑 ⚡️😖⚡️👍👍👍🙊👹🙊👹👍👍👍 ⚡️感恩相伴，尊享回馈！——用户是我们的上帝 ⚡️为了感谢您的支持，即日起，凡是推荐身边的朋友或同事使用8989看图王软件的老客户一律享受会员价的🫨折！ 🫨推荐3个朋友购买月卡赠送1张月卡！ 🫨.推荐2个朋友购买季卡赠送1张月卡！ 🫨.推荐2个朋友购买年卡赠送1张季卡！ 💸开卡续费联系客服 🥰@zizi6788888😤 💸备用客服号 🤑 @duojin_8989😤 💸双向机器人联系 🤑@zizi6788888_bot😤 ❤️🔥⚡️😖⚡️全新推出【8989看图王】买3送1可测试，祝各位老板发大财，天天爆单🥰🥰🥰🥰🥰🥰🥰
✨绘图大师·加密货币网银P图【其他均为病毒】 ， ✨绘图大师官方频道✨P图软件✨https://t.me/zuantuvi 😲📥以下为素材分类频道📥⚡️⚡️😍😍 😉【海王出海】 😉【网银转账】 😉【人设套图】 😉【聊天翻译】 😉【翻译软件】 😉【三国演义】 😉【中国素材】 😉【007 开户】 请鼠标往上面😊移动，挑选您可以点击蓝色字体
👈🤶人设套图素材业务如下：😉😉😉😄 😖🧐😞 0️⃣海外素材 @sucai_c8 1️⃣人设套图 @taotu_renshes1 2️⃣换脸大师 @facewapp 3️⃣电话轰炸 @hongzha_c8 4️⃣素材精聊 @huashuii8 5️⃣云湾海外 @cloudbays_fwp 6️⃣话术素材 @huashui66 7️⃣吃瓜猎奇 @chiguadashen1 8️⃣贷款数据 @dazhangguii999 9️⃣麻豆视频 @madou_91av ➕疯狂吃瓜 @nasachadang7878 ➕成人小说 @sesebooki 🧐😆🙂↕️ 😘@xiaolongtaotu 😘 @xn1314520 🥒🥒🥒🥒 请鼠标往上面😊移动，挑选
📱精选人设素材一直在持续更新最新人设素材 💻请大家持续关注👍频道😀以免上架错过更好的人设素材🥰祝您天天开大单，财源广进！分类素材频道如下🦜 😊海外素材 ⏩@sucai_taotu1 😊人设套图 ⏩@xiaolongtaotu 😊绘图大师 ⏩@huituruanjiang 😊客服系统 ⏩@Chat007_guanfeng 🇳🇿新西兰素 ⏩https://t.me/sucaille 🇯🇵日本素材 ⏩https://t.me/sucaillu 🇮🇹意大利素 ⏩https://t.me/sucaillw 🇺🇸美国素材 ⏩https://t.me/sucaills 🇰🇷韩国素材 ⏩https://t.me/sucailly 🇸🇬新加坡素 ⏩https://t.me/sucaillt 🇲🇽墨西哥素 ⏩https://t.me/sucaillo 🇲🇾马来西亚 ⏩https://t.me/sucaillr 🔼搜索方法：输入 “#关键词”，例…
小龙 人设素材 人设套图导航区，挑选好三方发编号或者转发给客服 https://t.me/xiaolongtaotu 😘❤️😊感谢新老客户的信任 🤤小龙人设套图素材业务如下：😭😜💋😌 生活素材【素材库 】 @sucai398 人设套图【亚洲女 】 @taotuio1 人设套图【亚洲男 】 @taotuio2 人设套图【欧美女 】 @taotuio3 人设套图【欧美男 】 @taotuio4 人设套图【女私密 】 @taotukt 人设套图【证件女 】 @taotuio6 人设套图【证件男 】 @taotukc 人设套图【PS图区 】 @meiguo07 绘图大师【钻图馆 】 @huitudashi5VIP 客服系统【007chat】 @Chatu007_guanfa…
【网友寻人】 北北 前段时间还在老挝说和男朋友分手了 然后到现在六天所有人都联系不上 不要伤害她 有线索联系我✈️：lexi468
🇰🇭马德望市警方抓捕50多名流浪汉、吸毒者和精神病患者，并将他们送往警局 ps：抓起来还得供饭吃，警方也算是干人事了
干丹卫生中心主任涉猥亵未成年被撤职 柬埔寨干丹省一名卫生中心主任因涉嫌在为一名未成年女患者治疗过程中实施不当行为，被撤销职务，并被暂停护士执业资格两年，警方同时正准备对其提起刑事诉讼。 涉事人员是塔克茂市Setbo卫生中心主任Chhun Phally。干丹省政府本周二宣布，把他免去卫生中心主任职务，调整为普通行政人员。 官方表示，经调查发现，他在为患者实施急救时，相关医疗操作不符合医疗及专业技术规范。 与此同时，柬埔寨国家护理委员会认定他的护理行为违反职业规范，决定暂停其护士执业资格两年。干丹省卫生局发布的决定显示，停牌期限到2028年8月10日。 塔克茂市警察局局长Yi Vanda表示，在完成行政处分后，警方已经着手准备刑事起诉程序。 警方指出，因为受害人是未成年人，本案涉嫌构成对未成年人实施猥亵并具有加重情节，目前正依据柬埔寨《刑法》第236条及第247条展开调查，案子还在进一步办理中。
柬新闻部长称泰军越境攻击铁证如山 柬埔寨新闻部长奈帕德拉8月7日表示，去年两轮柬泰边境冲突留下的大量现场证据，足以证明泰国军队曾对柬埔寨领土发动军事攻击，任何否认或宣传都抹不掉事实。 奈帕德拉当天在社交媒体发文，还配了多张边境受损照片，说现场留下的F-16和“鹰狮”战机空袭弹坑、集束弹等弹药残骸、受损民宅以及平民伤亡情况，都是冲突发生的直接证据。 他还指出，柏威夏寺、塔克拉贝寺等历史古迹在冲突中遭到破坏，同时有照片和资料显示，部分柬埔寨民众财物被掠夺，争议地区出现集装箱、铁丝网、道路封锁等设施，想制造既成事实。 奈帕德拉表示，柬方应该妥善保存、记录并核实所有证据，在适当时候提交国际社会，维护事实真相、追究相关责任，防止武力凌驾于国际法之上。 他最后强调：“真相不用高声呐喊，证据已经够了，世界终会作出判断。”
#柬埔寨新闻 吴哥国家管理局举办生态保护研讨会 多方研讨遗址林区与野生动物保护工作 2026年8月7日消息，吴哥国家管理局携手柬埔寨野生动物保护组织CWC，举办聚焦吴哥遗址森林及野生动物保护专题研讨会，共有60名执法人员、旅游行业从业者、遗址保护警察到场参会。 秩序局局长辛·皮西在开幕致辞表示，森林与野生动物是吴哥遗址不可分割的组成部分。本次研讨会设置多项课程，包含蛇类科普与蛇伤急救、护林巡逻实操技巧、景区现存生态难题、野生动物放归项目等议题。研讨会结束后，参训人员前往吴哥国家公园实地踏勘，实地察看林区现状以及动物放归相关工作，期望参训人员成为生态保护工作的实际执行者。 吴哥遗址除古建筑之外， 生态资源同样弥足珍贵。本次活动通过理论授课搭配实地研学，强化一线工作人员保护意识，推动遗址生态实现可持续保护。
#网友爆料：柬埔寨埔寨财通金运1园区物业负责人之一及G栋均设有属于个人办公室，G栋1-4层开设多个资金盘、越南盘，人称“豪哥”。 该项目原位于金运1别墅区V16栋，现长期频繁出进泰国、老挝与马来西亚，远程控制并开设多个资金盘和越南盘！ 豪哥，这次就先把你本人照片打码发出来，请尽快把事情处理了，再拖下去，下次发直接原图。再继续拖，查家人信息跟家人拿钱。（希望大家不要搞得那么难堪。） 祸不及家人，脸自己要的，我们只是要回我们自己该要的钱。最后……资料丢国内举报，大家只能鱼死网破了！ 麻烦身边关系跟着他，或者之前一起共过项目、关系好的，看到后转告他一下，避免牵连到其他无关人员。另外，也会把参与这个项目的所有老板、管理、操盘手的个人信息资料“牵扯”发出来。 各位大哥只能说声对不起，顶不住了，小弟也是被逼疯了！ 豪哥你好！我是V16栋项目杰哥总代理下面的一个小代理，这个项目90%的业务员都是我安排的。该项目今年5月2号全面收盘…
在金边超市打工五六年后终于自己开店，中国男子被熟客绑架转走巨款生死不明 一名在金边旧机场附近开超市的中国男子被熟人绑架后转走大量钱款，至今一年多仍生死不明，嫌疑人甚至直言：“我就是为了钱”。 在金边开超市的方女士（化名）称，她被绑架的外甥名叫游风声，此前一直在她的超市帮忙，前后有五六年时间。之后游风声在周边自主经营一家超市，不料外出送货时遭人设局绑架，至今下落不明。 方女士称，实施设局的是超市熟客老刘。老刘此前经常到超市消费，久而久之和方女士以及游风声相熟。方女士仅知晓老刘为湖北人，其余背景并不了解。 家属认为，游风声遭到绑架，极有可能是嫌疑人盯上了其父亲意外离世所得的赔偿金。游风声的父亲此前在工地发生事故去世，就在被绑架前不久，游风声刚刚拿到这笔赔偿金，资金存放于ABA银行以及汇旺账户内。 绑架案发当日，老刘与另一名嫌疑人叶胜江（近日被捕）等人租用一辆路虎车辆，还在周边租赁房屋当作埋伏地点。家属后续调取监控看到，涉案…
Showing the 12 most recent of 58 posts we hold for @hxsbl. 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 — 179,454 of 1,151,006entries 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 23 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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“《海峡时报》东南亚狗推快讯（曝光）📱‼️” (@hxsbl), 11,058 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/hxsbl.
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.