Channel
@BG_166
On this record: Growth · Engagement · Posts · Citations · Cite this entry
978subscribers
+26 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002731776186 |
|---|---|
| Type | Channel |
| Username | @BG_166 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/BG_166 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 11:39 | 978 | +26 |
| 6 Aug 2026, 22:25 | 952 | no change |
| 6 Aug 2026, 19:48 | 952 | first reading |
13 posts held, back to 6 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 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 13 (6 August 2026 – 6 August 2026) |
| Views total | 14 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 19:48 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.
#网友投稿，大量华人失业，30岁成就业分水岭。 以前来菲律宾找工作，只要愿意干，机会很多。现在岗位少了，竞争也变大了。随着菲律宾网络博彩（BC）行业持续收缩，曾经依靠行业红利发展的就业市场正在快速变化。 不少中国员工发现，过去高薪、低门槛的工作机会正在减少。 在菲多年从事相关行业的我表示，自己重新找工作时发现，如今企业不仅看经验，也开始关注年龄。“以前30岁不算什么，现在不少岗位更倾向年轻员工。” 过去几年，菲律宾相关行业快速扩张，大量中国人进入市场。很多普通岗位收入较高，吸引不少年轻人前往发展。 但随着监管加强、成本上涨以及市场需求下降，企业开始缩减规模，减少基层岗位，更重视技术、运营、管理等核心人才。 不少公司从过去大规模招聘，转向精简团队。客服、推广等基础岗位竞争越来越激烈，一些长期依赖行业经验的人开始面临转型压力。 对于部分在菲多年的华人来说，最大的问题不是离开，而是离开后还能做什么。多年积累的行业经验，在…
缅北果敢回忆录：老街黑暗往事——从“淘金天堂”到人口贩卖链条 曾经的缅北果敢老街，在很多人眼中，是一个充满机会的地方。有人带着发财梦来到这里，有人相信所谓的“高薪工作”，踏上了一条改变人生的路。 但在一些幸存者的回忆里，老街的另一面，却隐藏着一条黑暗产业链。 招聘广告、高薪诱惑、熟人介绍……这些曾经是很多人进入果敢的第一步。有人以为自己只是来做客服、销售、技术岗位，却没想到等待自己的可能是限制自由、暴力控制，甚至成为犯罪集团交易链上的一环。相关调查显示，缅北部分地区曾存在以诈骗园区为依托的人口贩运、非法拘禁等犯罪行为。 在一些案件中，武装力量、地方势力和犯罪团伙之间复杂的关系，也让普通人难以逃离。一些受害者回忆，他们进入园区后，护照被扣押，行动受到限制，想离开需要支付高额“赎金”，甚至有人被转卖到其他地方。 果敢老街曾经灯火通明，赌场、酒店、园区林立，但繁华背后，是无数人的血泪经历。有人被骗走青春，有人失去自由，有人背…
#网友曝光: 这个P图中介公司帮他们设计图案头像P图业务后，帐不结，一直拖着，最后消息也不读不回了，希望大家同行看见后擦亮眼睛别白忙活了哦！
#网友吐槽：柬埔寨金边某华物业真是好样的！ 原来你们的财富就是这样讹诈出来的！不只是我一家遇到这样的问题！吞外来投资者的大楼那么多，现在连我们这种小店面、小公司的资产也不放过！ 打算搬家，提前讲好了，结果昨天让保安来威胁不让走。我们自己报警开了脸书直播，然后给我们签署一堆文件说可以，今天又和房东串通说我们不交物业费不可以走，还用警察来威胁我们，结果我们一开直播一录视频又立刻跑，你们属什么的啊？ 我们从去年开始就跟你们说过，我们是正规公司，要开税票的，结果你们直接说你们公司还有很多物业公司从来不开票，搞笑呢，柬埔寨的法律只是制定给我们外国投资者的吗？本地人公司不用遵守？
昨晚马来西亚吉隆坡丹湖城移民厅突击检查外籍公寓社区。现场抓了缅甸人，印尼人，中国人加起来一百多人。 没护照和无法出示劳工签证的直接拷起来带走。
#吃瓜视频：今晚芭提雅海边人妖大战，该说不说这老人妖子是真有劲，看着都痛。
#泰国春武里府夜市群体冲突事件 8月5日凌晨，泰国春武里府一处夜市发生一起群体冲突事件。一群人在现场发生争执，随后升级为多人互相打斗，现场一度陷入混乱。
#泰国资讯：孔敬府两名男子涉嫌性侵未遂被捕，警方展开调查 8月5日，泰国孔敬府班潘县发生一起涉嫌性侵未遂案件。两名年轻男子在饮酒后，于蓬沙旺水库公园内对一名独自行走的女子实施侵犯行为。 据初步了解，事发时，两名男子将该女子强行拖入公园公共厕所，企图实施性侵。女子在遭遇威胁后奋力反抗，并大声呼救，最终迫使两人未能得逞。 事后，两名嫌疑人迅速逃离现场。警方接到报案后展开调查，并根据相关线索将两名涉案男子抓获。目前，案件正在进一步调查处理中，警方将依法追究相关责任。
#泰国春武里府夜市群体冲突事件 8月5日凌晨，泰国春武里府一处夜市发生一起群体冲突事件。一群人在现场发生争执，随后升级为多人互相打斗，现场一度陷入混乱。
#马来西亚资讯：古晋公寓河畔惊险一幕 中国籍女子跳河获友人与保安跳水挽救 一名中国籍女子今日凌晨疑因轻生跳河，同行的中国籍男子见状立即跃入河中施救，所幸一名公寓保安也奋不顾身跳河协助，最终在消拯员救援下，两名中国籍男女成功获救。 此次行动共出动7名消拯员，以及1辆消防车及1辆紧急医疗救援车救援行动于凌晨3时45分受控，救援行动于凌晨4时18分圆满结束。
#网友，两个小姐姐在大街上打起来了，满屏都是白腿，看服装应该是一个鸡窝的小姐。
#阳泰集团骗子盘口 网友曝光：阳泰集团骗子盘口，专骗预付，不要上当受骗。我已经被骗了8900U，目前已经被他踢出群聊，被拉黑。怪我自己没有专群作业，希望大家引以为戒。 从开始的付款，到后面的狗推反馈，会员一直加，从1000U预付到了9000U，现在一分没有退。 业务员和主管唱双簧空放，主管又和总监开唱双簧。第一天的单子可以推到第二天，不能飞单，讲怕会员直接付错码。 9000U的教训，大家可以看一下。
Showing the 12 most recent of 13 posts we hold for @BG_166. 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 — 234,132 of 1,169,250entries 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 41 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“东南亚狗仔队-热点新闻” (@BG_166), 978 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/BG_166.
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.