Channel
@THXWDNY
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
105subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002274479298 |
|---|---|
| Type | Channel |
| Username | @THXWDNY |
| Description | 头号新闻|新闻大事件|曝光平台 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/THXWDNY |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 09:01 | 105 | no change |
| 6 Aug 2026, 19:48 | 105 | first reading |
5 posts held, back to 9 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 9 August 2026 |
|---|---|
| Posts held | 5 (9 August 2026 – 9 August 2026) |
| Views total | 9 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 09:01 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 9 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 3 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.
在tiktok主动加的我然后加了飞机号，说自己是中泰烟总代理，可以给我代理价格，然后我也就相信了，他说全世界都可以发货，我开始抱着试试的态度，就发了3条烟，给转账540人民币，结果过去十多天了见不到东西单号也没有，每天用各种理由话术来推辞，所以我要曝光一下别让更多的同胞受害上当受骗. . ✈️大陆一二三线城市 ✈️菲律宾🇵🇭 ✈️柬埔寨🇰🇭 ✈️阿联酋🇦🇪 ✈️新加坡🇸🇬 ✈️泰国曼谷 ✈️越南合群 ✈️马来西亚 ✈️斯里兰卡 ✈️麻豆影视 ✈️新闻事件 ✈️客服24小时🉑开会员
盗窃空置园区？西港警方逮捕4名嫌疑人 今天上午，西港4分区行政警察局联合当地民防力量，在西港4分区4村4组一处废弃大楼内成功破获一起撬门入室盗窃案。 行动中，警方当场抓获4名涉案嫌疑人。目前，嫌疑人已被移交西港市警察局，以便接受进一步讯问并依法按法律程序处理。 关注海外大事件👉 投稿👉 . . ✈️大陆一二三线城市 ✈️菲律宾🇵🇭 ✈️柬埔寨🇰🇭 ✈️阿联酋🇦🇪 ✈️新加坡🇸🇬 ✈️泰国曼谷 ✈️越南合群 ✈️马来西亚 ✈️斯里兰卡 ✈️麻豆影视 ✈️新闻事件 ✈️客服24小时🉑开会员
#马来西亚资讯：吉隆坡一KTV曝员工遭持枪恐吓及殴打事件，涉事老板被指涉嫌违规持有警用配枪 近日，一起涉及娱乐场所员工遭暴力对待及持枪恐吓的事件在当地引发关注。据网络爆料称，吉隆坡一家华裔经营的KTV内，一名外籍女员工因工作安排问题与管理层发生分歧，随后 allegedly 遭到店方负责人暴力威胁。爆料内容更指，涉事负责人曾持有疑似警用制式配枪，对女员工实施恐吓及殴打。 据爆料者描述，事发当晚，该名外籍女员工因排班、工时等工作安排向管理层提出疑问。双方最初属于正常工作沟通，但随后矛盾升级。爆料称，涉事KTV负责人没有选择通过正常方式解决纠纷，而是联系相关人员，并取得一把疑似警方制式配枪。 随后，涉事负责人返回员工工作区域，并以枪械对女员工进行威慑。据称，在场员工当时受到惊吓，现场气氛一度十分紧张。 更令人关注的是，爆料称，该负责人不仅使用枪械进行恐吓，还对女员工实施推搡、殴打等行为，并以报警、投诉以及工作等问题对其进行威…
#网友投稿：🇲🇾柔佛洲“新山市”，TAXX上海俱乐部今天凌晨被移民局突击检查，当场抓走了几十个小姐姐，还有一些证件不齐全的中国人。 关注海外大事件👉 投稿👉 . . ✈️大陆一二三线城市 ✈️菲律宾🇵🇭 ✈️柬埔寨🇰🇭 ✈️阿联酋🇦🇪 ✈️新加坡🇸🇬 ✈️泰国曼谷 ✈️越南合群 ✈️马来西亚 ✈️斯里兰卡 ✈️麻豆影视 ✈️新闻事件 ✈️客服24小时🉑开会员
网友投稿：金边Kantaok分区老机场附近居民楼，一名女子与男友吵架后欲跳楼轻生。目前警察已在楼下铺设安全垫。 ☎️ 免费爆料投稿找： 👨👨👧👧 东南亚头条吃瓜：. . ✈️大陆一二三线城市 ✈️菲律宾🇵🇭 ✈️柬埔寨🇰🇭 ✈️阿联酋🇦🇪 ✈️新加坡🇸🇬 ✈️泰国曼谷 ✈️越南合群 ✈️马来西亚 ✈️斯里兰卡 ✈️麻豆影视 ✈️新闻事件 ✈️客服24小时🉑开会员
Showing the 5 most recent of 5 posts we hold for @THXWDNY. 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 — 127,225 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 51 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“头号新闻 | 东南亚🌏” (@THXWDNY), 105 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/THXWDNY.
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.