Channel
@dongnanya_DJ
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
65,160subscribers
+1,164 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002381078513 |
|---|---|
| Type | Channel |
| Username | @dongnanya_DJ |
| Description | 商务合作联系：t.me/Flau0228 投稿 @ccvvcc2020 副管理： t.me/yysd8886 你是我最漂亮的扶手也是我下不了的头，后来柬埔寨的风再也吹不到我的心里，我爱的人也离我而去，没有你的包厢变的好大好大，大到我都不敢相信这是东南亚 柬埔寨大事件 @JPZDSJ 东南亚大事件 t.me/JPZDSJ886 灰产：t.me/HCBGDSJ 西港挣钱西港花，柬埔寨男人不回家 菲律宾不会下雪，马尼拉也没有爱情 龙争虎斗彼岸花，缅甸才是你的家 |
| Created | Between 1 September 2024 and 31 March 2025— 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 | 6 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/dongnanya_DJ |
National news — 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 47% 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 6 other registered channels. 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 |
|---|---|---|---|
| @dongnanya_DJ/40992 · this entry7 Aug 2026, 16:37 UTC | @dajian995/261057 Aug 2026, 16:39 UTC | 1.00 | 2 minutes |
| @dongnanya_DJ/40994 · this entry7 Aug 2026, 16:37 UTC | @dajian995/261077 Aug 2026, 16:39 UTC | 1.00 | 2 minutes |
| @dongnanya_DJ/40995 · this entry7 Aug 2026, 16:37 UTC | @dajian995/261087 Aug 2026, 16:39 UTC | 1.00 | 2 minutes |
| @dongnanya_DJ/41011 · this entry7 Aug 2026, 17:00 UTC | @dajian995/261257 Aug 2026, 17:02 UTC | 1.00 | 2 minutes |
| @dongnanya_DJ/41015 · this entry7 Aug 2026, 18:14 UTC | @dajian995/261297 Aug 2026, 18:14 UTC | 1.00 | under a minute |
| @dongnanya_DJ/41024 · this entry7 Aug 2026, 20:57 UTC | @dajian995/261377 Aug 2026, 20:58 UTC | 1.00 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @dajian995 | 10 (8/8 hand-verifiable sample passed) | 1.00 | 72 seconds | this entry (9–1) |
| @TGXWDSJBL | 10 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (10–0) |
| @JPZXWDSJBL | 10 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (10–0) |
| @JPZDSJ | 9 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (8–1) |
| @JPZDSJ886 | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (9–0) |
| @HCBGDSJ | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (9–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. 2 of the 2 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 20 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 7, the earliest publisher we hold is @dongnanya_DJ — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 8 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 6 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 |
|---|---|---|
| 12 Aug 2026, 08:52 | 65,160 | -1,396 |
| 11 Aug 2026, 08:33 | 66,556 | -95 |
| 10 Aug 2026, 10:11 | 66,651 | +4,105 |
| 9 Aug 2026, 11:01 | 62,546 | -430 |
| 8 Aug 2026, 13:16 | 62,976 | -1,020 |
| 7 Aug 2026, 17:02 | 63,996 | first reading |
125 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 12 August 2026 |
|---|---|
| Posts held | 125 (7 August 2026 – 12 August 2026) |
| Views total | 32,592 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 19:12 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 32 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.
高脚苏总骗出国索高额赔付 高脚苏总，福建安溪人，安排路线把我从国内弄到柬埔寨绿巨人园区。他朋友的公司做精聊，我在国内就明确说了不做，他还多次用高薪忽悠我出国。 到了绿巨人园区后干了一个月，我说不做了想回国，对方就要高额赔付。没办法，只好安稳干了七个月。后来公司说要搬去七星海，我没去，两个月工资也没发。 高脚又让我去中国城金水园区9栋3楼333办公室做法国刷单，说工资会补。结果在那边又干了一个月，我说工资不要了，就要回国。他联合主管阿木一起给我算了1.6万赔付。我当时威胁报警，他说报警也没用，给钱才能走。最后找朋友给了他1万U，才放我出园区。 跟我一起从国内出来的兄弟一直跟着他干，我没要代理费也没要介绍费。兄弟辛辛苦苦跟了一年多，公司搬去波贝后他还继续跟着。结果波贝大检查，公司解散，高脚直接不管死活，也不安排回国。现在这货自己都回国了，压根不管下面人。 我现在只想要回那1万U赔付钱。三天内联系我，不给的话后续继续曝光。 广…
#菲律宾 #鸿运 #十一 #偷吃回扣 先给你留点做人的尊严，敏感信息先打码。今天不想把事做绝，你自己清楚走支付通道时干了哪些偷鸡摸狗的事。 你公司人好像叫你十一。我不管你在鸿运偷吃了多少商户回扣，找车队跑那些分公司不知道的业务，你干的缺德事自己心里有数。阿飞不知道、小六不知道、新一不知道，你当所有人都傻？国内有车有房的人，跑来干这种下三滥的事？从园区到马卡提，你还算个人吗？表面装人样，钱包里动了多少手脚你自己清楚。 话说到这你也能猜个八九不离十了。你问我为啥爆你？吃公司的我不管，吃相难看是你自己的事，但不守信用丢鸿运的脸，还威胁到我的利益，玩女人玩到我头上了，操你妈的！ 当初和土豆、飞机CJ_tianyue在钱包账户里搞小动作的事，你以为我不知道 有房有车，在菲还搞个小三，你可以的，巴适得很。你大概知道我是谁了，大家都是园区出来的。找小编要我联系方式，明天中午12点前没说法，我就先去码，然后各大站点全网曝光，同时国内安…
#缅甸亚太买人狗高额索赔 这个买人的狗东西，在亚太做人事招聘。我介绍一个朋友进去上班，才干了十天就受不了体罚和高压，提出辞职。 对方公司居然要高额赔付，6060U加69600人民币，进的时候可是零赔付。大家记住这个狗人事，账号xz168168、awei168168111。 之前在亚太村外，现在人又被买到将军山去了。这种货大家千万别碰。 广告赞助商，均已上押担保 ——————————————— ➖➖➖🔥🔥🔥🔥🔥➖➖➖ 柬埔寨大事件 灰产曝光 二手车买卖 西港二手群 柬埔寨求职 金边二手群 柬埔寨聊天交友 男人俱乐部 🛎 ☎️爆料与广告联系：@Ccvvcc2020
在东南亚混久了，人都废了。不是赚钱的问题，是脑子出了问题。 以前在国内，花100块都得掂量掂量。到了这边，100美金刷出去眼睛都不眨一下。不是因为你赚得多了，是因为你把美金当冥币花了——数字小，没感觉，花完拉倒。 月底一看账单：“卧槽，这钱是我花的？”不是你是谁？鬼帮你花的？ 你以为自己在过好日子，其实就是在给东南亚打工。会所、酒吧、请客吃饭，样样不落。回国一看银行卡，余额还没你脸皮厚。 兄弟，你在国内省吃俭用，攒三万块能活半年。在那边大手大脚，三万美金只够买几个月的“面子”。面子有了，钱没了，人老了，啥也没剩下。 更蠢的是啥？你觉得这种生活正常。没存款正常，月底吃土正常，借钱发工资也正常。你管这叫“活在当下”，其实就是被这边的节奏带沟里了。 一句话：你是来赚钱的，不是来过瘾的。钱是挣来的，也是守住的。守不住，赚再多都是过路财神。别等到回国那天，才发现自己在国外潇洒了几年，实际上是在给别人的好日子买单。 广告赞助商，…
#骗子曝光 #陈帅宇 陈帅宇，贵州安顺的挂壁仔，手机号18593810761，专门卧底配合警察钓鱼抓偷渡的。 这狗东西贵州佬四处骗人，各个公司都接他，他还同时联系多家公司让人买票去接。自己一直作妖，一会儿说护照直接卡关，一会儿又说要验资没钱，就让人转钱、开酒店吃喝玩乐。 结果到了昆明人直接玩消失，联系不上了。死妈的货，望各公司赶紧避雷，千万别再接这人！ 广告赞助商，均已上押担保 ——————————————— ➖➖➖🔥🔥🔥🔥🔥➖➖➖ 柬埔寨大事件 灰产曝光 二手车买卖 西港二手群 柬埔寨求职 金边二手群 柬埔寨聊天交友 男人俱乐部 🛎 ☎️爆料与广告联系：@Ccvvcc2020
代办证件垫付费用请尽快归还 有认识这两个人的帮忙问一声，之前让人代办的证件还要不要？哪怕直接说不需要了也行。 请把我帮你们垫付的费用还回来，证件你们拿走，账单我这边都留着。 大半年了，你俩是没钱还是怎么的？至少给个消息吧。 最后再给一个星期时间自己联系我处理。下周二前还没信的话，就把你们所有个人信息发国内反诈警察，本地警局同步入档备案。别他妈再装死了。 广告赞助商，均已上押担保 ——————————————— ➖➖➖🔥🔥🔥🔥🔥➖➖➖ 柬埔寨大事件 灰产曝光 二手车买卖 西港二手群 柬埔寨求职 金边二手群 柬埔寨聊天交友 男人俱乐部 🛎 ☎️爆料与广告联系：@Ccvvcc2020
泰国又出现一种很恶心的新骗局。 一名23岁女大学生近日向“สายไหมต้องรอด”求助称，自己因为经济压力，在网上看到有人自称“有钱老板”，表示只是想找女生视频聊天解闷，不需要见面，还愿意帮忙承担生活费、学费。 女生觉得“不见面应该安全一点”，于是选择视频通话。 结果对方在通话过程中不断诱导她做越来越私密的动作，之后声称会付款，却突然挂断并拉黑。 两天后，事情彻底失控。 女生发现，自己的视频通话画面已经被偷拍视频，并被上传到网络和所谓“秘密群组”中，脸没有打码，还附带个人资料和赌博网站链接。 更严重的是，她后来发现，疑似还有10多名受害者遭遇同样套路，其中包括学生、名校大学生，甚至有艺人。 目前，相关求助机构已联系泰国网络警察，准备进一步追查涉案人员。 📣关注东南亚悬赏-🍉吃瓜中心 🔋Trx能量手续费兑换 @Trx523 ☎️ 欢迎投稿爆料： @BG770
🤩🤩🤩🤩🤩🤩🤩🤩品牌铸就非凡 · 实力绝非偶然 ➡️ 超级玩家赌神附体，狂揽1.6亿，可自行验证真伪 😀注册网址： y30491.com ⚡️⚡️⚡️⚡️⚡️⚡️ 😀😳😳😀😳😳😀😳😳😀😳😳😀😳😳 #东南亚盘总们首选最权威综合😃台 集团储备资金2亿U 打造全网最牛逼的线上娱乐平台。 1️⃣1️⃣1️⃣1️⃣1️⃣1️⃣ 1️⃣1️⃣1️⃣1️⃣1️⃣1️⃣ 📣Y3国际 #真人视讯限红50万u一口 😀😀😀😀😀😀😀😀😀#电子可3000U一拉 😀Solaire千亿实体资本，菲律宾索莱尔·官方直营 😘Y3精彩时刻： 女王大水 玩家在PG电子赏金女王盈利450万U PP电子糖果大水玩家在PP电子极速糖果盈利380万 麻将胡了爆大分 玩家在PG电子麻将胡了盈利420万 【#Y3国际｜全网福利天花板】 单笔出款50万 彩金3888 单笔出款100万 彩金8888 单笔出款300万 彩金3…
菲律宾经营连锁超市的中国老板遭绑架，绑匪索要100万美元赎金，监控录像曝光 据菲媒报道，事件发生于8月2日深夜。监控画面显示，当晚11时39分50秒，受害男子正驾驶一辆黑色轿车准备倒车，一辆白色面包车突然从后方将其截停。 车上迅速冲下5名持枪劫匪，其中有人持有AK47，强行将受害者押上面包车。 11点40分15秒左右，白色面包车离开现场。从拦截到将人挟持带离，绑匪仅用了不到25秒，动作极度干练利落。 据报道，绑匪向受害者家属索要100万美元赎金，并要求以加密货币形式支付。幸运的是，8月4日，该男子趁绑匪醉酒防备松懈之际，带着手铐翻窗逃脱并成功报警。 截至本文发帖，当地警方已抓获其中3名中国籍绑匪及1名涉嫌协助租车的本地女子，尚有2名嫌犯在逃。 广告赞助商，均已上押担保 ——————————————— ➖➖➖🔥🔥🔥🔥🔥➖➖➖ 柬埔寨大事件 灰产曝光 二手车买卖 西港二手群 柬埔寨求…
#柬埔寨 #李岩虎 #阿宗 #坑人真相 不认识阿宗之前，他一直做盘口业务员和出码生意。2024年10月，他把老家一个人卖进绿巨人园区，拿了卖人的1.5万U去打牌。那人在里面被打得全身是伤，手也被电棍打肿，还在办公室跪了一下午。 晚上那人联系他姐，说要从宿舍楼楼顶跳下去。他姐找当地公安局的朋友，公安又联系到我，多方托关系才把人从绿巨人救出来送回国。 这只是其中一件，别的我不提，反正这事是我经手的，我清楚原委。不管怎么样，我绝不会卖自己兄弟，老家的外地的都不行。 因为这事我才知道有阿宗这个人。后来他在外面输钱，吃住都成问题，想去公司上班，开口就要当总监，保底3000U，全盘净利润拿10个点。碰上大扫荡，事情搁置了。他跑去越南，吃住还是没着落，又联系我。同乡的能帮就帮，他说自己以前干过跨境电商，也起过盘。我让他去波贝当管理，他过去后嫌老板抠，让我先申请预支家里用的钱，没给，他就觉得没自由、太压抑，一直鼓动在外面起盘让他操盘。我…
诺顿大学校刊点名陈志 8月11日，柬埔寨高考结束后的第二天，诺顿大学推出全新校刊《The Herald》，整本超过百页，内容涵盖校友风采以及国内外热点事件。 比较引人注意的是，这期校刊还专门把电诈、网赌等网络犯罪治理列为重点议题，并点名介绍太子集团掌门人陈志涉嫌跨国网赌电诈的案件。 校刊从所谓“年轻企业家”的形象讲起，介绍其商业发展以及后续被指涉及跨国犯罪的相关情况，并借此提醒即将进入大学的年轻人，提高对网络犯罪和诈骗活动的警惕。 据报道，中柬两国警方此前展开联合调查，陈志于2026年1月6日在柬埔寨被捕，随后被押解回中国。 学校这波操作也算挺直接，拿真实案例给学生上了一课：别被所谓“年轻企业家”“高回报项目”这些包装忽悠了，网赌电诈背后可不是闹着玩的。 至于网友最后调侃的那句——“不知道当年文森特赞助过这所学校没有～～”，目前没有可靠信息能够证实这件事，吃瓜归吃瓜，还是别把未经证实的说法当事实。 广告赞助商，均已…
苹果研发照片来源验证技术 苹果正在研发一项新的照片来源验证技术，未来可能帮助用户确认一张照片是不是由 iPhone 相机真实拍摄。 据悉，这项技术可能结合相机硬件、系统签名以及加密认证机制，为照片生成一套可以验证的来源信息。 简单来说，以后看到一张照片，或许可以通过相关认证信息判断它是不是来自真实的 iPhone 拍摄，而不是AI生成或后期大幅修改的图片。 随着生成式AI越来越猛，现在P图、造假照片已经变得非常容易，普通人想判断一张图到底是不是真的，确实越来越难。 苹果如果把设备级认证做起来，相当于给照片加上一层“身份证”，让图片来源更加容易追溯。 不过目前这项技术仍处于研发阶段，苹果还没有公布具体上线时间以及最终实现方式，能不能真正解决AI图片造假的问题，还得等官方后续消息。 广告赞助商，均已上押担保 ——————————————— ➖➖➖🔥🔥🔥🔥🔥➖➖➖ 柬埔寨大事件 灰产曝光 二手车买卖 …
Showing the 12 most recent of 125 posts we hold for @dongnanya_DJ. 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 — 920,166 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 11 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.
@dongnanya_DJ 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.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“🇰🇭 柬埔寨🇰🇭 包厢文化-大事件” (@dongnanya_DJ), 65,160 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/dongnanya_DJ.
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.