Channel
@RG898
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
14,950subscribers
+9,709 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003011822366 |
|---|---|
| Type | Channel |
| Username | @RG898 |
| Description | 吃瓜频道 有会员的亲朋好友们帮助推一下，万分感谢！免费投稿爆料： 广告合作 @WG868 |
| 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 | 13 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/RG898 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 the other topics.
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 in near-verbatim form on 3 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts 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 |
|---|---|---|---|
| @ML465/1219 Nov 2026, 14:36 UTC | @RG898/5854 · this entry10 Nov 2026, 07:58 UTC | 1.00 | 17 hours |
| @ML465/13010 Nov 2026, 03:25 UTC | @RG898/5864 · this entry11 Nov 2026, 04:58 UTC | 1.00 | 26 hours |
| @ML465/14710 Nov 2026, 11:25 UTC | @RG898/5876 · this entry11 Nov 2026, 10:58 UTC | 1.00 | 24 hours |
| @ML465/17511 Nov 2026, 07:19 UTC | @RG898/5892 · this entry12 Nov 2026, 02:58 UTC | 1.00 | 20 hours |
| @ML465/18611 Nov 2026, 16:06 UTC | @RG898/5917 · this entry13 Nov 2026, 05:58 UTC | 1.00 | 38 hours |
| @ML465/19912 Nov 2026, 05:54 UTC | @RG898/5921 · this entry13 Nov 2026, 08:58 UTC | 1.00 | 27 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @ML465 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 25 hours | @ML465 (6–0) |
| @qbj7777 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 28 hours | @qbj7777 (6–0) |
| @knmkio | 6 (6/6 hand-verifiable sample passed) | 0.99 | 24 hours | @knmkio (6–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. 18 of the 18 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 44 comparable posts for this entry, running 7 August 2026 to 13 November 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.
Of the group of 3 channels, the one whose matching posts we hold earliest is @ML465. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 14 November 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 is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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 |
|---|---|---|
| 13 Nov 2026, 11:01 | 14,950 | +3 |
| 9 Nov 2026, 11:15 | 14,947 | +10,049 |
| 5 Nov 2026, 17:46 | 4,898 | +5 |
| 2 Nov 2026, 13:49 | 4,893 | -14 |
| 30 Oct 2026, 16:16 | 4,907 | -11 |
| 27 Oct 2026, 22:31 | 4,918 | -15 |
| 25 Oct 2026, 03:55 | 4,933 | -4 |
| 21 Oct 2026, 23:45 | 4,937 | -2 |
| 18 Oct 2026, 15:07 | 4,939 | -13 |
| 15 Oct 2026, 15:46 | 4,952 | -20 |
| 13 Oct 2026, 02:10 | 4,972 | -25 |
| 6 Oct 2026, 08:01 | 4,997 | -36 |
| 29 Sept 2026, 09:37 | 5,033 | -66 |
| 15 Sept 2026, 17:40 | 5,099 | -29 |
| 12 Sept 2026, 04:15 | 5,128 | -21 |
| 8 Sept 2026, 06:18 | 5,149 | -13 |
| 2 Sept 2026, 16:16 | 5,162 | -14 |
| 30 Aug 2026, 22:13 | 5,176 | -5 |
| 28 Aug 2026, 03:58 | 5,181 | -16 |
| 24 Aug 2026, 20:06 | 5,197 | first reading |
61 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 18 pages of 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. It is computed over the 1 of 38 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 61 (7 August 2026 – 14 November 2026) |
| Views total | 2,966 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 23:39 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 14 November 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 1 video 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 3 of the 61 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 61 most recent posts we hold, published 7 August 2026 to 14 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram’s own ‘edited’ marker: 0 of 38 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
#缅甸掸邦打击网络诈骗 逮捕759名外国人 含中国公民502名时间：2026年11月12日一、执法成果2026年8月1日至10月31日，掸邦打击网络诈骗，逮捕外国人759名，含中国公民502名。二、作案手法主要针对中国公民，以交友恋爱、虚假投资、高薪工作、抽奖奖金、假赌博平台等方式诈骗，并利用AI及Deepfake伪造名人形象和新闻网站行骗。三、关联犯罪 窝点多在边境地区，兼涉洗钱、人口贩运。四、后续措施继续打击境内网络诈骗；提醒公众不点可疑链接、不泄露密码和OTP，发现线索及时举报。
#网友投稿 视频中绑匪为缅甸木姐人林飞，长期诱骗绑架勒索敲诈中国人，至少50人以上的家属均被他敲诈过。图片中为他目前扣押中国人及虐待证明 现场关人的电话：09674887017、09662547214 经常用的车子是3M-5719黑色皇冠、5058牌照尾号黑色皇冠、8899牌照白色皇冠 被他勒索交过赎金的名字有向海江、谢德祥、王昱皓、代朝燕、王鹏超、林嘉艺、王武、艾子豪、罗广鑫、黄凯祥、李佳恒、张春浩、王大鹏、陈建林、郝志杰、陈郑、李俊咖、苗武庆、吴凤波、李厚超、吴鹏程、吴润峰、秦栎茗、陆凯，童宽、鹏源义、席进财等等共计50人以上。以上人员已经全部在联系家属并提供绑匪真人视频，受害者家属请联名向中国警方施压，务必严惩境外绑匪 注：绑匪同谋和操作者也是木姐人真实名字叫：岳永开，小名压柱。飞机号小柒。同谋堂哥飞机名好好钓鱼
#网友投稿 本人与老乡吃饭时，认识了柬埔寨西港独立大道长沙杨裕兴饭店老板，化名强别（许文强） 一个地方的老乡，经常照顾他的生意，去店里吃饭，还经常帮他打打广告、介绍生意。 发表这篇文章之前，朋友告诉我，还在给他的店送餐。当时聊起这件事，正在他店里请客吃饭，身边的朋友都听到了。他说认识老板，和老板是兄弟，有面子，还说菲律宾那里好赚钱，可以过去看看。 当时听信了他的一面之言，考虑到他是做生意的，有自己的店，而且又是一个地方的老乡，所以并没有怀疑。 到了菲律宾后，对方安排人接待，然后说帮忙办理签证，随后收走了护照，开车直接把本人带到了园区，进了盘口。想出去时，保安也不肯放行，说要得到Boss同意。这时才发现，很多事情都不一样了。 （同时，中间发生了很多倒霉、气人的事情，就省略吧。）也导致手机、行李什么都没有了。所以，等处理好换洗衣服与手机，重新登录所有社交账号、联系朋友后，结果签证也逾期了。 后面联系他本人，说自己要走，如果…
#网友曝光 此女子本人23年在特区认识她，她跟我说她弟弟赌博输了好几十万要我借5万给她，把她弟弟救出来，出于好心就借给她了，后面我回国了给了一个微信号给她，她说她会加我微信并且尽快还给我，直到26年10月也没有加我。可是缘分就是这么的造人，让我们10月又在特区碰到了，我就问他为什么不加我微信，她又是一顿卖惨，后面我知道她是故意不想还我，我随便找了一个借口试探一下她，让她先还1万，谁知道她这么没格局把我拉黑了。她本人现在在特区水街《夜来香会所》做小姐兼职做扶手，估计上班是假，套客人是真，请大家不要上当受骗
#网友投稿 现在黑客是真的嚣张啊，赶紧都早点去死吧！今天晚上我们电脑就被黑客入侵了，飞机给我发消息，我直接拉黑了。 然后他就用我飞机各种给好友发消息，说要搞死我。没想到这个坏种直接给我客户发消息截图，把客户点死了。 你在公司活不下去，快被电死了，看在我这里搞不到钱，就搞点事。活不起就早点去死，出来祸害人！你这种逼人就是自己活不起了，也见不得别人好。要知道你是谁，一刀给你捅了。在东南亚，死个人就像死条狗一样，你就是那条狗！ 也告知一下大家，用翻译器都要小心。现在大环境这样子，遇到这种黑客，只能认倒霉了。这人太缺德玩意了，一直在操控我这边电脑，从凌晨到上午没停过，把我客户点得死死的
#网友投稿 致东南亚扶手 踏入缅甸就是羊入虎口 近期妹子被绑架的曝光帖子比较频繁 ，今天有个知情网友说了一个惊天内幕。 缅甸某些黑园区已经把绑架扶手做成了产业，他们会专门在东南亚发布泰国包养女孩子骗到园区绑架勒索强*** 他们会去各大包养群发布重金包养信息，引诱去缅甸地区接单，诱骗过去再对其进行 勒索， 开火车，敲赔付等，该园区作案已数起，近期也有不少国内的妹子中招 （36岁女子赴泰旅游，被骗缅甸电诈园区 ）。据说还有国内的小网红也被骗过去。 不要以为金主重金包养做发财梦，这些人已经把绑架扶手做成了产业链，一旦进入缅甸园区，就要付出巨额代价。小姐姐们注意安全吧！
#网友投稿 渣女缅甸名字叫 နန်းခင်နုနွယ်，公司名字叫 #安娜。她本人现在在776/771山上园区上班，做刷群。跟我谈了三年恋爱，之前她长得好胖，我都不嫌弃，一直给她幸福快乐的。要金子、要手机，我都给她买还有去年亚太跑路的时候，也看着可怜她，还带她一起回去的。然后去柬埔寨上班，遇到中国老幺，肯定是被中国人放进去了吧？还继续骗我感情和我的钱。她自己跟中国人玩了后，传到爱死病，说什么我传给她的。你他妈的，跟老子不在一起一年了，要是我有病，应该早就死了吧？动不动就说让我赔偿她的生命。你自己骚了，被老幺玩死的人。本来不想曝光的，想让网友的朋友们多注意这个s货。要是还来一直烦我，我就发你的做爱视频给大家看。最后警告你一次，不想再丢脸就不要来烦你爹，我是不会客气谁的，
#网友爆料 一个坐车不给钱的cs王八蛋，各位兄弟朋友注意‼️ 此人飞机名字叫做：大师，上个月找我约车，柬埔寨到曼谷，车费2500u，因为之前送人过，我同意让他到付，谁知道这个人cs一个，人偷渡到曼谷就逃跑了 也就这点格局，路费都付不起，你约nm的车，现征集此人照片，他经常在交克瓦雷一带活动，各大中介也擦亮眼睛，不要跟他交易！
#网友投稿 有时候我会想，自己是从什么时候开始对键盘产生这种奇妙的依赖感的。 刚进公司的时候，对键盘其实是陌生的，敲字只是工作的一部分，是完成任务的工具。 可这几年下来，我在一段段和客户的对话中，一次次敲击键盘，慢慢地开始感受到那种节奏与表达带来的微妙变化。 每一个字从指尖落下，都像是有温度的、有情绪的，不再只是冷冰冰的符号，而是承载着沟通、理解，甚至一点点情感的延伸。 渐渐地，我发现自己开始享受这种感觉，甚至不再满足于普通的办公键盘，会去在意手感、声音、反馈。 当我坐在工位上，没有客户聊天的时候，手指竟会不自觉地发痒，仿佛在等待下一次敲击的开始。
#网友爆料 这些盗U的傻逼真是死m的东西，事情的原因是这样的，我是一名公司的财务，我们公司是做日本盘的，今天刚有一笔5万U的款入金进来，被盗U的傻逼给盗了。 就是图片上这个人，他们给我发的广告，我想着闲来无事打一下试试，结果就是他们给我发的链接，我进去玩了一个小时赢了1000多U，下分的时候，我绑定了我自己的收款地址，我手机上公司公户上的5万U就没有了，我被公司主管在办公室打了1个小时，操你妈的盗U狗。 现在的盗U技术这么牛逼吗，点了链接进去玩了一会UU就没有了，大家一定要以我为戒，不要随便点陌生的长链接。
#网友投稿 此路不通！现在想从缅甸走小路回中国，真没那么容易了。 上个星期三，我们老大硬塞了一个人情单，要把一个从缅甸腊戌出发的人通过边境小路送回中国。老大也是个明事理、懂时局的人，只交代我们尽力而为，能把人安全送过去最好。 经过三天在边境徘徊、观察和等待，到了星期六，我们自认为准备得差不多了，便安排两名缅甸边境原住民带人正式出发。 没想到出发不到五个小时，整队人就失联了。起初我们并不意外，但超过十二个小时仍联系不上，基本判断这次走小路回中国失败了，很可能已经被抓。 说说现在中缅边境走小路的情况。以我七年的带队经验来看，从中国走小路进入缅甸，成功率不到25%；从缅甸走小路回中国，成功率更是不足15%。这些只是我个人的经验判断。 嘿嘿，情况就是这么个情况。不是夸，也不是吹，中国边防武警的人员素质和装备水平确实很强。我认为他们能不能抓到偷渡人员，很多时候不是能力问题，而是想不想抓的问题。 干了七年这一行，我越来越觉得，现…
🌟🌟🌟🌟🌟 今天这两位大哥成功赢走二十几万。最近欧亚国际娱乐平台路子一直挺不错的哦，无聊时想搏一搏，试试手气的各位领导们，欢迎咨询全天在线客服 公司下载官网🌐 www.5553318.com 公司下载官网🌐 www.5559918.com ❗️❗️❗️❗️❗️❗️❗️ 首充赠送%10永久有效 +返点+洗码费 领取彩金请联系客服 t.me/ou989 彩金双向机器人客服 t.me/ou989
Showing the 12 most recent of 61 posts we hold for @RG898. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 95 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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“特区吃瓜/缅甸吃瓜/勐拉吃瓜/佤邦吃瓜/曝光吃瓜” (@RG898), 14,950 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/RG898.
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.