Telegram RegisterThe public register of Telegram
Telegram profile photo for 东南亚吃瓜爆料

Channel

东南亚吃瓜爆料

@pu599

2 usernames

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

9,753subscribers

-14,502 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002539460326
TypeChannel
Usernames@ofutt @pu599
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 September 2026
Measurements held52
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/pu599

Growth

9,75324,27117,0127 August 2026 — 24,255 subscribers7 August 2026 — 24,255 subscribers8 August 2026 — 24,256 subscribers8 August 2026 — 24,262 subscribers9 August 2026 — 24,263 subscribers10 August 2026 — 24,267 subscribers10 August 2026 — 24,270 subscribers10 August 2026 — 24,271 subscribers11 August 2026 — 24,265 subscribers11 August 2026 — 24,240 subscribers12 August 2026 — 24,212 subscribers13 August 2026 — 24,154 subscribers13 August 2026 — 24,154 subscribers14 August 2026 — 23,815 subscribers14 August 2026 — 23,814 subscribers15 August 2026 — 23,361 subscribers16 August 2026 — 23,139 subscribers17 August 2026 — 22,907 subscribers17 August 2026 — 22,907 subscribers18 August 2026 — 22,713 subscribers18 August 2026 — 22,677 subscribers19 August 2026 — 22,414 subscribers19 August 2026 — 22,312 subscribers20 August 2026 — 22,068 subscribers20 August 2026 — 22,068 subscribers21 August 2026 — 21,728 subscribers21 August 2026 — 21,657 subscribers22 August 2026 — 20,930 subscribers23 August 2026 — 20,709 subscribers24 August 2026 — 19,717 subscribers24 August 2026 — 19,472 subscribers25 August 2026 — 16,805 subscribers25 August 2026 — 14,965 subscribers26 August 2026 — 14,425 subscribers26 August 2026 — 14,425 subscribers27 August 2026 — 14,082 subscribers27 August 2026 — 13,858 subscribers28 August 2026 — 13,363 subscribers28 August 2026 — 13,142 subscribers29 August 2026 — 12,902 subscribers29 August 2026 — 12,494 subscribers30 August 2026 — 12,233 subscribers31 August 2026 — 12,031 subscribers31 August 2026 — 11,999 subscribers1 September 2026 — 11,824 subscribers1 September 2026 — 11,636 subscribers2 September 2026 — 11,604 subscribers2 September 2026 — 11,300 subscribers3 September 2026 — 10,971 subscribers3 September 2026 — 10,585 subscribers4 September 2026 — 10,498 subscribers5 September 2026 — 9,753 subscribers7 August 20265 September 2026
52 measurements spanning 29 days, net -14,502. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 7,575–26,449 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 52
Measured (UTC)SubscribersChange
5 Sept 2026, 17:009,753-745
4 Sept 2026, 13:4010,498-87
3 Sept 2026, 20:0110,585-386
3 Sept 2026, 01:4310,971-329
2 Sept 2026, 12:5311,300-304
2 Sept 2026, 01:2511,604-32
1 Sept 2026, 13:1611,636-188
1 Sept 2026, 02:3411,824-175
31 Aug 2026, 14:5411,999-32
31 Aug 2026, 01:3512,031-202
30 Aug 2026, 12:2612,233-261
29 Aug 2026, 23:5612,494-408
29 Aug 2026, 13:4312,902-240
28 Aug 2026, 21:5813,142-221
28 Aug 2026, 17:0813,363-495
27 Aug 2026, 20:4513,858-224
27 Aug 2026, 18:1414,082-343
26 Aug 2026, 19:0314,425no change
26 Aug 2026, 15:0614,425-540
25 Aug 2026, 17:2914,965first reading

Engagement

532 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 53 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.94%
avg views ÷ 9,753 subscribers
Avg views / post
969
532 posts measured
Reaction rate
0.063%
reactions ÷ views · ER floor
Posts in window
532
of 532 held

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 10 of 532 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held532 (7 August 20262 September 2026)
Views total515,739
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 01:35 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.

What this channel posts

Video runtime
2h 07m
Average length
48s

Measured directly from 160 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.

Reaction mix

8 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
675.0%
🔥112.5%
🥰112.5%

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 10 of the 532 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 532 most recent posts we hold, published 7 August 2026 to 2 September 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.

Recent posts

2 Sept 2026, 14:57 UTC≈2,660 views1 reactionsread 3 September 2026
Photo

#东南亚相关爆料说明:宝威与天行高层存在收割代理行为,已有大量代理离职。 若公司运营正常,代理人员不会轻易离职。代理为公司创造收益后,若提成过高,公司可能采取回收措施。此类情况并非首次,已引发普遍不满。本人作为基层员工,原计划与公司共同发展,但实际情况与预期不符。建议有意入职者谨慎考虑宝威与天行。 对仍在宝威与天行任职的代理提出警示:当前代理的遭遇可能预示未来类似情况。本人曾担任宝威代理线,离职后提成未获发放。近日观察到,离职代理的E换账户已被冻结。据悉公司E换系统可追踪代理转账金额。 公司推出的E换功能存在可控性。宝威与天行当前运营状况存疑,集团是否介入管理?建议相关部门核查凯旋2楼相关情况。 天行公关无需进行解释。宝威与天行过往操作,业界多有了解。若部门出现1000万负盈利却无法发放薪资,员工感受如何?公司信誉缺失,高层处理方式存疑。清水被架空、安迪离职等事件,疑与前期收割相关。建议询问水部长900万提成是否已领取。

1

2 Sept 2026, 14:28 UTC≈1,780 viewsread 3 September 2026
Photo

#东南亚吃瓜爆料:讲讲我被绑架的经历(真实故事)不要和陌生人说话! 在柬埔寨居住近4年,主要在园区活动。某晚在金边一家本地酒吧独自饮酒时,一名中国男子主动搭话,询问停留时长、工作及住址等信息。出于礼貌,双方互加联系方式。 数日后,该男子邀约再次喝酒,地点为同一家酒吧。聊天中涉及个人关系、朋友及回国计划等内容,信息半真半假。此后连续数日饮酒。最后一次饮酒时,该男子以取衣物为由,指示前往停车场取车内物品。抵达停车场后,二人强行将本人拖入车辆,持匕首威胁,实施捆绑并堵住口鼻,同时取走手机。 车辆行驶至陌生地点后,本人被带入一处房屋,室内另有3人(2名四川籍、1名东北籍)。绑匪询问家庭经济情况及资金来源,取出手机内不足1万U资金后,迫使本人向家属打电话索要资金。首次索要30万元人民币,家属转账后,绑匪继续要求追加50万元。本人表示无力支付后遭受殴打,并被要求继续筹款。后续数日,本人被限制睡眠、遭受折磨,绑匪拍摄视频发送给家属施压。

2 Sept 2026, 14:01 UTC≈3,920 viewsread 3 September 2026
Photo

在东南亚,若缺乏以下任一行为特征,则难以立足 第一品·假义气 张嘴称兄弟,实际暗中算计 酒桌承诺豪爽,散场即删除联系 第二品·反着来 帮过你的人,立即拉黑 你帮过的人,持续催促回报 第三品·抠门精 点贵菜后迅速买单离开 随份子后立即借钱补足 第四品·看人下 对穷者排斥,对富者奉承 喊哥记账,递烟时暗中使绊 第五品·吹与装 白天夸大其词,晚上精打细算 发圈炫耀财富,实际收入隐瞒 第六品·不要脸 借钱时低姿态,还钱时高姿态 左手签协议,右手即否认 第七品·嘴抹蜜 外貌出众者称养得起,容貌平平者夸有才华 缺点说成优点,功劳归为运气 第八品·只进不 红包只抢不发,饭局只蹭不请 礼物只收不送,钱财只入不出的 第九品·没底线 跪地谋利,站立空谈 良心低价出售,脸皮高价获利 第十品·挂羊头 满口正义,实际敛财 高谈大义,实为设套 第十一品·每日想 早起自问:今日坑谁 睡前自思:是否吃亏 第十二品·三副脸 对上司逢迎,对

2 Sept 2026, 13:50 UTC28 viewsread 3 September 2026
Photo

#群友爆料:老挝万象,三江阿玛尼酒店相关人员老杨,办公场地位于Long Vien Golf Club高尔夫球场内三联排别墅及三江阿玛尼酒店11楼,收取高额物业费。 初期曾承诺场地安全,并展示与老挝公安部合影照片。出现问题后,相关人员失去联系,押金未退,亦未提供处理方案。 以上为场地、车牌号及相关人员在老挝本地女友照片。如不处理,将持续发布场地及人员照片。现代轿车为老杨所有,商务车为阿玛尼酒店接驳专用,另有一台现代商务车。 其飞机及WS单独对接,疑似准备撤离。目前其他物业仍在运营,建议老挝公安部与中国公安部门调查三江阿玛尼酒店内相关盘口,提醒有合作意向者注意。 ☎️ 免费爆料投稿找:@Pu551 👨‍👨‍👧‍👧 东南亚吃瓜爆料:@Pu599

2 Sept 2026, 13:04 UTC≈1,660 viewsread 3 September 2026
Video

#群友爆料:缅甸木姐105码莫东村涉嫌诈骗集团 8月14日收到同盟军消息后,提前8小时撤离,由民团和同盟军持枪押送员工至安全屋,全天看守。 集团负责人:光头强。核心人物:六哥、山东、太保。集团高管核心人物包括代理老板:海洋、孟昊、福全、西门。 该集团现已返回园区正常办公,呼吁中缅执法部门清剿此集团,解救被困人员,并调查背后保护伞。光头强使用车辆为黑色牧马人及白色雷克萨斯。 ☎️ 免费爆料投稿找:@Pu551 👨‍👨‍👧‍👧 东南亚吃瓜爆料:@Pu599

2 Sept 2026, 12:55 UTC≈1,640 viewsread 3 September 2026
Photo

拒绝改写 该文本片段详细描述了电信诈骗(电诈)、跨境贿赂警察、逃避执法检查、转移犯罪窝点等明确违法犯罪行为。根据安全准则,我无法协助改写、润色或传播此类内容。 ☎️ 免费爆料投稿找:@Pu551 👨‍👨‍👧‍👧 东南亚吃瓜爆料:@Pu599

2 Sept 2026, 12:37 UTC≈1,570 viewsread 3 September 2026
Photo

🇱🇰斯里兰卡批准与中国签署移民合作备忘录,双方将共享情报打击偷渡和人口贩运 斯里兰卡内阁批准与中国签署移民监管合作谅解备忘录,以加强签证、移民管理及出境事务合作。该备忘录由斯里兰卡移民和出入境事务部与中国国家移民管理局签署,旨在便利两国官员及公民从事商业、投资、旅游、科学和技术活动。双方将加强官方信息和情报交流,深化打击人口贩运、组织移民偷渡等跨国有组织犯罪合作。此外,双方计划举办移民管理官员培训研讨会并开展能力建设项目,提升执法合作水平。备忘录草案已获外交部、海外就业和旅游部及总检察长批准。 ☎️ 免费爆料投稿找:@Pu551 👨‍👨‍👧‍👧 东南亚吃瓜爆料:@Pu599

2 Sept 2026, 12:37 UTC≈2,450 viewsread 3 September 2026
Photo

#最新消息:西港凯迪有人员被宪兵逮捕,后续或有进一步行动。 ☎️ 免费爆料投稿找:@Pu551 👨‍👨‍👧‍👧 东南亚吃瓜爆料:@Pu599

2 Sept 2026, 12:11 UTC≈1,610 viewsread 3 September 2026
Photo

#温馨提示:近期有不法分子冒充平台客服,以赠送特邀彩金为由实施诈骗。 骗子常用流程: ① 发送虚假平台链接,诱导用户注册; ② 要求下载App并授权相册权限; ③ 若冷钱包助记词存储于相册中,可能导致数字资产被盗; ④ 用户使用赠金盈利后,提款时需先充值提款金额的一半,充值后资金可能被骗取。 提醒:凡以注册送彩金为名义的活动,多为杀猪盘或盗取数字资产诈骗。请勿贪图小利,以免遭受损失。 ☎️ 免费爆料投稿找:@Pu551 👨‍👨‍👧‍👧 东南亚吃瓜爆料:@Pu599

2 Sept 2026, 12:01 UTC≈3,180 viewsread 3 September 2026
Video

#网友反馈:西港中国城金水附近有大量警察、宪兵及政府人员进行挨家挨户检查,附近人员请注意。 ☎️ 免费爆料投稿找:@Pu551 👨‍👨‍👧‍👧 东南亚吃瓜爆料:@Pu599

2 Sept 2026, 12:00 UTC≈1,780 viewsread 3 September 2026
Video

🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🤩亿级域名|78.COM 🤩官方飞投|充提自由 🤩NO钱包担保3亿U|可查验! 😀 东南亚大事件联合担保🤩🤩🤩🤩🤩(电子) 📱官方频道:@DF78 ➡️关注领VIP 🔝大品牌,实力派:大發 78.COM 本身就是最好的辨识度。 ✅香港六合彩 · 独家盈利无上限! 🤩所有的特码🤩🤩倍,封顶赔率! 🤩连码三中三🤩🤩🤩倍 🤩连码四中四🤩🤩🤩🤩🤩倍 🤩百家乐全网最高返水🤩% 🤩电子|棋牌|捕鱼返水🤩.🤩% 🤩十三水|德州自主组队,无抽佣; 🏆百家乐真人视讯台红🤩🤩万U; 💥新人超会赢,大發精彩时刻分享: 🥇六合彩 玩家用7个号码组合下注连码三全中(35注)➕四全中(35注),每注100U,结果开出4个号码。命中4注878倍及一注10000倍大奖,稳稳落袋135万U; 🥈PG电子 8月17号,壹玩家游戏中爆出200万U大奖,本金仅用2万U; 🥉DB真人 玩百家乐的老板,第一天存款50万U,连续7天

2 Sept 2026, 11:45 UTC10 viewsread 3 September 2026
Photo

#最新消息:帝豪随后也在开展抓捕行动。 ☎️ 免费爆料投稿找:@Pu551 👨‍👨‍👧‍👧 东南亚吃瓜爆料:@Pu599

Showing the 12 most recent of 532 posts we hold for @pu599. 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.

Mentions

Named by 5 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.

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.

Cite this entry

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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“东南亚吃瓜爆料” (@pu599), 9,753 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/pu599.

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.