Channel
@YT667
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
15,086subscribers
-538 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002920505715 |
|---|---|
| Type | Channel |
| Username | @YT667 |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/YT667 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 19:53 | 15,086 | -46 |
| 28 Aug 2026, 20:13 | 15,132 | -41 |
| 27 Aug 2026, 23:26 | 15,173 | -26 |
| 26 Aug 2026, 22:07 | 15,199 | -6 |
| 25 Aug 2026, 22:23 | 15,205 | -16 |
| 24 Aug 2026, 20:38 | 15,221 | -42 |
| 23 Aug 2026, 08:47 | 15,263 | -31 |
| 21 Aug 2026, 21:36 | 15,294 | -30 |
| 20 Aug 2026, 18:28 | 15,324 | -8 |
| 19 Aug 2026, 16:23 | 15,332 | -17 |
| 18 Aug 2026, 17:03 | 15,349 | -37 |
| 17 Aug 2026, 16:27 | 15,386 | -21 |
| 16 Aug 2026, 14:16 | 15,407 | -52 |
| 14 Aug 2026, 21:08 | 15,459 | -14 |
| 13 Aug 2026, 12:25 | 15,473 | -32 |
| 12 Aug 2026, 14:07 | 15,505 | -10 |
| 11 Aug 2026, 14:06 | 15,515 | -20 |
| 10 Aug 2026, 10:37 | 15,535 | -27 |
| 9 Aug 2026, 11:01 | 15,562 | -33 |
| 8 Aug 2026, 09:13 | 15,595 | first reading |
25 posts held, back to 24 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 45 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 28 August 2026 |
|---|---|
| Posts held | 25 (24 July 2026 – 28 August 2026) |
| Views total | 3,819 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 16:05 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 9 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.
#国内资讯：北京警方今年打掉170个涉诈窝点和团伙，截获6200余万元现金及19.51公斤黄金 8月27日发布的北京警方最新反诈数据显示，今年以来，北京电信网络诈骗发案数和群众财产损失金额同比均下降超过50%。 北京市公安局刑侦部门8月26日介绍，今年以来，警方持续打击涉诈电话卡、银行卡以及人员、资金转移链条，累计打掉170个涉诈窝点和团伙。 针对诈骗资金由线上转账向线下现金、黄金等实物转移的新变化，北京警方开展专项打击，目前已抓获460余名涉诈资金线下转运嫌疑人，打掉73个涉诈资金转运车队，截获现金6200余万元、黄金19.51公斤。 警方同时加强涉诈风险预警和劝阻，将预警信息按照紧急、高、中、低四个等级进行处置，通过96110反诈专线、短信、智能语音和上门劝阻等方式及时干预。今年以来，已避免群众潜在损失超过40亿元。 今年3月，丰台警方在一起虚假投资诈骗预警中及时介入，阻止一名群众继续转账，避免潜在损失700万元。…
#网友投稿：大家好，我想告知大家巴基斯坦的局势非常糟糕！ 请所有在巴基斯坦工作的成员务必小心，联邦调查局（FIA）正在突击搜查多个办公室。如果还有人在办公室工作，请暂时居家办公，或者干脆停工几天。这次他们展开了大规模的行动，规模很大。 昨晚他们突击搜查了G6和G9两处私人别墅，幸好我们成功逃脱。 关注导航频道➡ @dh555 投稿 @YT858
#柬埔寨资讯：金边雷西郊区查获两处电诈窝点 抓获4名涉案人员 昨晚，金边市雷西郊区区长亲自带队，对辖区内两处涉嫌网络诈骗的窝点展开突击检查。 行动共抓获4名嫌疑人（3名柬籍、1名马来西亚籍），查封大批作案工具，包括585部手机、154张以上外籍电话卡、24台电脑/显示器、21台主机及1辆汽车等。 目前，嫌犯与缴获证物均已移交金边市警局依法处理。 熊屁股里面塞手机 终究还是没躲过～～ 关注导航频道➡ @dh555 投稿 @YT858
#泰国资讯：美国男子在曼谷行窃后袭警被捕 8月22日，一名美国公民在曼谷三攀他旺区一家7-Eleven便利店行窃后逃跑，追捕过程中用裁纸刀袭击交警，致其重伤。 受伤警长普拉桑·苏卡尼（56岁）颈部被严重割伤，已送医急救。嫌疑人亚历山大·特洛伊·洛佩兹（29岁）约半小时后被警方抓获。 警方称，该男子DU品检测呈阳性（疑似冰DU），精神不稳且拒不配合调查。他将面临袭警、盗窃、抢劫及谋杀未遂等指控。 PS：最近泰国不安全 关注导航频道➡ @dh555 投稿 @YT858
#群友投稿：8月21日，在万象-廊开第一老泰友谊大桥，老挝公安部特别行动组继续将第六批64名泰国公民（其中28名为女性）移交给泰国当局，以便依法进行起诉。 这礼拜交接三批去泰国了，惨哦这些阿泰😂 关注导航频道➡ @dh555 投稿 @YT858
西港警方破获网诈涉DU案，逮捕35人！ 昨天，西港市行政指挥部对位于4分区5村的“海岸公寓”展开突击行政清查，成功破获一起涉嫌网络诈骗及DU品犯罪案件。 行动中，警方当场查获一体机电脑14台、手提电脑10台、手机17部、短款气枪1支（含1个弹匣）、短刀1把以及部分疑似DU品等作案工具。 现场共抓获35名涉案人员（含4名女性），包括涉嫌网络诈骗的12人（10名越籍、2名中籍）、涉毒的2人（1名中籍男、1名越籍女），以及无有效护照非法居留的21人（18名中籍、3名越籍）。 目前，所有涉案人员及收缴物证已被移交西港省警察局作进一步调查审理。 关注导航频道➡ @dh555 投稿 @YT858
🇲🇾 中国女子吉隆坡机场大闹 喊叫威胁言论被安保带走 据网友在Reddit爆料，昨天，一名疑为中国籍的女子在马来西亚吉隆坡国际机场1号航站楼登机口附近大吵大闹。 目击者称，该女子使用中文直播并叫嚣威胁言论。随后一名同行男子试图夺下手机并拉走她未果。该女子甚至现场开始倒计时，造成现场混乱。约15分钟后，机场安保人员赶到将该女子带离现场，航班秩序恢复正常。 目前，大马相关部门尚未对此发布通报。 关注导航频道➡ @dh555 投稿 @YT858
#币圈资讯：币安被指向俄罗斯提供客户数据 导致援乌人员被捕 据路透社获取的法律文件显示，全球最大加密货币交易所币安（Binance）去年向俄当局提供客户捐款明细，致俄籍IT专家Yuri Belenkiy因向乌军捐款逾700美元而被控“资助恐怖主义”并被捕。 此举引发对其违反欧盟数据保护法的指责，因币安曾于2023年9月宣称全面退出俄罗斯市场。币安对此予以否认，称仅依法配合全球执法机构的合法调取要求。目前，该受害者仍羁押于俄狱中等待审判。 这件事真正值得关注的，不只是“币安有没有提供数据”，而是一个更现实的问题：当加密货币平台全面进入合规时代后，所谓的匿名与隐私，到底还能剩下多少？ 关注导航频道➡ @dh555 投稿 @YT858
西港宪兵打掉一个卖假苹果手机的犯罪团伙，4名中国籍嫌疑人被移送法办 8月8日，接获受害者报案后，西港省宪兵司令兴文迪指挥专项行动，在西港市1分区成功抓获4名涉嫌兜售假手机的中国籍男女（2男2女）。 经查，该团伙以真iPhone 17 Pro Max及发票诱骗买家，收钱后顺手牵羊换成假手机逃离。宪兵在现场缴获假iPhone 17 Pro Max 14部、现金1660美元及46.2万瑞尔、护照3本及发票等物证。 目前，西港省初级法院法官已下令将4人依法提审并羁押候审。 西港人才依然多～～ 关注导航频道➡ @dh555 投稿 @YT858
#群友投稿：中国餐馆遭遇马来西亚槟城24K老大东田黑社会性质团伙打砸抢恶性事件。 我是一名在马来西亚提供当地就业服务机会的发展者，也是一名中国餐饮创业者。 于2026年7月31日21点45分，有一团伙组织——槟城24K东田黑社会性质团伙，闯入我的店铺进行打砸抢，采取极其恶劣的暴力手段，将我店铺员工殴打至伤。当时我们一心求安稳，抱着“多一事不如少一事”的心态，没有选择报警。可退让换不来安宁。 该团伙黑社会性质组织于2026年8月11日晚上19点左右，团伙成员四十多人公然闯入我店铺内，再次实施打砸抢恶性事件。进场第一时间，他们破坏闭路监控，意图销毁现场第一时间的视频证据，并实施更加极其暴力的手段殴打店内工作人员，导致厨师被打成重伤，目前正在抢救室治疗，至今仍在医院昏迷不醒；其他店内员工也仍在医院接受伤情治疗。 我们本本分分开店做生意，只想安稳生存、创业发展，却遭遇如此恶性团伙组织的暴力事件。目前，我手中留存有大量现场相关证据…
#柬埔寨资讯：班迭棉吉省波贝市检查行动 查获17名外国人 8月12日，班迭棉吉省联合工作组在波贝市开展外国人员居住情况检查行动，共检查8处建筑设施，发现17名外国人。 此次行动由班迭棉吉省省长吴瑞直接指挥，相关部门联合开展。检查中发现的17名外国人均持有效证件，具备合法居留资格，其中包括9名女性及泰国籍人员。据了解，检查地点主要涉及住宅楼、出租房及教育机构等场所。除一处发现泰国籍人员在当地赌场工作外，其余地点未发现外国人员居住，也未发现任何可疑物品。 班迭棉吉省政府表示，相关部门将继续加强对外国人员及重点区域的检查管理，维护当地社会治安秩序。 关注导航频道➡ @dh555 投稿 @YT858
#群友投稿：今天凌晨在马来西亚雪兰莪州锡米山，抓了几百个外劳，缅甸人居多，还有少于居住在那边的中国人。 关注导航频道➡ @dh555 投稿 @YT858
Showing the 12 most recent of 25 posts we hold for @YT667. 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,006 of 1,626,711entries 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 2 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“全球华人资讯🌎” (@YT667), 15,086 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/YT667.
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.