Telegram RegisterThe public register of Telegram

Channel

东南亚大事件(吃瓜曝光)

@Ag811

2 usernames

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

37,690subscribers

-1,190 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002667663432
TypeChannel
Usernames@Ag811 @sviprr
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 live13 August 2026
Measurements held14
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/Ag811

Growth

37,69038,88038,2857 August 2026 — 38,880 subscribers7 August 2026 — 38,880 subscribers7 August 2026 — 38,854 subscribers8 August 2026 — 38,749 subscribers8 August 2026 — 38,661 subscribers9 August 2026 — 38,575 subscribers9 August 2026 — 38,389 subscribers10 August 2026 — 38,310 subscribers10 August 2026 — 38,209 subscribers11 August 2026 — 38,201 subscribers11 August 2026 — 38,043 subscribers12 August 2026 — 38,008 subscribers12 August 2026 — 37,757 subscribers13 August 2026 — 37,690 subscribers7 August 202613 August 2026
14 measurements spanning 5 days, net -1,190. 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 37,512–39,059 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:4437,690-67
12 Aug 2026, 22:4437,757-251
12 Aug 2026, 01:3338,008-35
11 Aug 2026, 21:1338,043-158
11 Aug 2026, 02:0238,201-8
10 Aug 2026, 22:5538,209-101
10 Aug 2026, 01:4238,310-79
9 Aug 2026, 19:2138,389-186
9 Aug 2026, 05:0138,575-86
8 Aug 2026, 21:5238,661-88
8 Aug 2026, 07:3238,749-105
7 Aug 2026, 19:3738,854-26
7 Aug 2026, 18:1838,880no change
7 Aug 2026, 18:1838,880first reading

Engagement

139 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 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.75%
avg views ÷ 37,690 subscribers
Avg views / post
1,030
139 posts measured
Reaction rate
0.112%
reactions ÷ views · ER floor
Posts in window
139
of 139 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 73 of 139 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 12 August 2026
Posts held139 (7 August 202612 August 2026)
Views total143,857
Reactions total74
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 20:41 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
2m 43s
Average length
7s

Measured directly from 25 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

74 reactions across 73 posts, in 9 distinct kinds. The most used accounts for 18.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1418.9%
😁1418.9%
🎉1013.5%
🥰912.2%
👏810.8%
🤩79.46%
🔥68.11%
56.76%
11.35%

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

Measured over the 139 most recent posts we hold, published 7 August 2026 to 12 August 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

12 Aug 2026, 17:31 UTC270 viewsread 12 August 2026
Video

👉🏻灰产吃瓜 @Sviprr 👉🏻吃瓜曝光 @Xocow 👉🏻东南亚大新闻 @Bc716 😮吃瓜群众 @Ton5c 😮色色吃瓜 @Eysiy 😮吃瓜搞笑 @cg776 😘欧美 @Uowey 😘欧美2 @xigot 😘欧美3 @Ofutt 😘日本无码 @Daacy 😘日本Fac @Rav266 😘日本中文字幕 @Eycco 😘 国产无码 @Vojoj 😳表情包 https://t.me/pu229/7 😚色频解除教程 https://t.me/pu229

12 Aug 2026, 16:09 UTC≈2,680 views1 reactionsread 12 August 2026
Video

#外卖配送员与保安冲突事件 ☎️ 免费爆料投稿:@Pu222 👨‍👨‍👧‍👧 东南亚大事件:@Sviprr

👍1

12 Aug 2026, 15:48 UTC≈4,480 views1 reactionsread 12 August 2026
Video

#白色汽车撞人事件 ☎️ 免费爆料投稿:@Pu222 👨‍👨‍👧‍👧 东南亚大事件:@Sviprr

😁1

12 Aug 2026, 15:40 UTC≈1,670 views1 reactionsread 12 August 2026
Video

集美地区因摊位争占引发的冲突事件。 ☎️ 免费爆料投稿:@Pu222 👨‍👨‍👧‍👧 东南亚大事件:@Sviprr

🔥1

12 Aug 2026, 15:26 UTC≈2,620 views1 reactionsread 12 August 2026
Video

揭阳市一驾驶员疑为躲避交警检查而紧急掉头,事件责任归属待定。#吃瓜 #每日瓜讯 ☎️ 免费爆料投稿:@Pu222 👨‍👨‍👧‍👧 东南亚大事件:@Sviprr

🎉1

12 Aug 2026, 15:16 UTC≈2,740 views1 reactionsread 12 August 2026
Video

健身房内出现不符合常规的着装情况,引发关注。 #吃瓜 #每日瓜讯 ☎️ 免费爆料投稿:@Pu222 👨‍👨‍👧‍👧 东南亚大事件:@Sviprr

1

12 Aug 2026, 14:56 UTC50 viewsread 12 August 2026
Photo

An individual described their initial experience with fetishistic behavior involving personal apparel. They identified a woman's residence in the same complex through repeated observation and retrieved a pair of shoes containing white socks from outside the door. These items were used for masturbation in a stairwell, during which one sock was retained and the shoe returned to its original position. The account noted

12 Aug 2026, 14:49 UTC47 views1 reactionsread 12 August 2026
Video

#吐口水 泼水节活动,参与者玩得开心。 ☎️ 免费爆料投稿:@Pu222 👨‍👨‍👧‍👧 东南亚大事件:@Sviprr

1

12 Aug 2026, 14:18 UTC≈1,660 views1 reactionsread 12 August 2026
Photo

马德望省警员涉网络斗鸡赌博 警长下令彻查、属实即严惩 社交媒体流传在职警员“洪某”现身隐蔽赌点、参与在线斗鸡赌博的照片,引发关注并损害警队形象。 马德望省警察局长丹英本章已下令人事部门立案调查。快反小组将核实身份,若属实,将依规从严处理,并追查赌点开办者及同伙刑事责任。 ☎️ 免费爆料投稿:@Pu222 👨‍👨‍👧‍👧 东南亚大事件:@Sviprr

🤩1

12 Aug 2026, 14:02 UTC≈2,230 views1 reactionsread 12 August 2026
Photo

洪玛玛耐澄清:退出柬老越三角区 发展东北部绝不牺牲主权 8月12日,洪玛耐首相在上丁省表示,柬老越发展三角区(CLV-DTA)设立初衷为推动东北部基础设施建设与经济发展,从未涉及主权损害。该机制覆盖三国13省,运行约25年。柬埔寨已于2024年9月正式退出,以回应民众关切。 退出后,三国双边合作持续推进,东北部仍为发展优先领域。无论框架存废,柬方发展均不以牺牲国家主权为代价。 ☎️ 免费爆料投稿:@Pu222 👨‍👨‍👧‍👧 东南亚大事件:@Sviprr

😁1

12 Aug 2026, 13:52 UTC37 viewsread 12 August 2026
Photo

妙瓦底清查鱼机赌博:半月查 13 起、抓 164 人、扣 79 台游戏机 克伦邦议会副主席质询指出,妙瓦底市区存在大量鱼机赌博厅,造成噪音扰民、毒害青少年,并成为毒品交易及盗抢分子藏匿场所,要求专项取缔。 官方通报(截至8月4日)打击成果: 立案查处13起 抓获164人(男99人、女65人) 缴获赌资259.5万缅元、游戏机79台 当局表示,将持续军警联动、深挖情报,力争彻底根除全市鱼机赌博活动。 ☎️ 免费爆料投稿:@Pu222 👨‍👨‍👧‍👧 东南亚大事件:@Sviprr

12 Aug 2026, 07:19 UTC≈3,330 views1 reactionsread 12 August 2026
Video

8月10日下午,四川攀枝花市乡菜郎特色延边菜餐厅发生一起食品安全事件。部分顾客食用该店提供的野生菌类后出现中毒症状。 ☎️ 免费爆料投稿:@Pu222 👨‍👨‍👧‍👧 东南亚大事件:@Sviprr

👍1

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

Citation-graph rank — 747,224 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.

Mentions

Named by 3 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“东南亚大事件(吃瓜曝光)” (@Ag811), 37,690 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Ag811.

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.