Telegram RegisterThe public register of Telegram
Telegram profile photo for 东南亚/吃瓜/搞笑曝光

Channel

东南亚/吃瓜/搞笑曝光

@ggyifan88

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

23,584subscribers

-9,418 since we began measuring on 29 August 2026

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

Register entry

Telegram ID-1001553677078
TypeChannel
Username@ggyifan88
Description🌍 涵盖 #东南亚 #柬埔寨 #菲律宾 #缅甸 #泰国 #迪拜 #斯里兰卡 #越南 #马来西亚 奇趣无限,欢乐天下! 《奇趣天下》以“好看、吃瓜、搞笑、好玩、好奇”为核心理念,让群友在欢笑中解压,在网络中开眼界,在搞笑与舞蹈中感受激情 东南亚奇趣/百科 东南亚最新/最热 东南亚搞笑/幽默 东南亚吃瓜生活故事! 包涵国内新闻/吃瓜🍉 建议您选择理性性观看! 东南亚交流群 @taxcc 投稿建议联系官方✈️ @qsjt_7
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live18 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/ggyifan88

Topic

Adult — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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.

Growth

12,89333,00222,947.529 August 2026 — 33,002 subscribers30 August 2026 — 32,942 subscribers31 August 2026 — 32,826 subscribers1 September 2026 — 32,062 subscribers2 September 2026 — 30,504 subscribers3 September 2026 — 30,170 subscribers4 September 2026 — 29,267 subscribers7 September 2026 — 25,664 subscribers10 September 2026 — 23,493 subscribers12 September 2026 — 18,009 subscribers14 September 2026 — 13,095 subscribers15 September 2026 — 12,893 subscribers18 September 2026 — 23,584 subscribers23,58429 August 202618 September 2026
13 measurements spanning 19 days, net -9,418. 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 9,877–36,018 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 02:3923,584+10,691
15 Sept 2026, 21:4012,893-202
14 Sept 2026, 06:4013,095-4,914
12 Sept 2026, 16:3718,009-5,484
10 Sept 2026, 16:2023,493-2,171
7 Sept 2026, 10:4125,664-3,603
4 Sept 2026, 17:2029,267-903
3 Sept 2026, 02:1830,170-334
2 Sept 2026, 00:2430,504-1,558
1 Sept 2026, 01:3532,062-764
31 Aug 2026, 03:0632,826-116
30 Aug 2026, 05:3532,942-60
29 Aug 2026, 19:0133,002first reading

Engagement

144 posts held, back to 29 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 14 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.067%
avg views ÷ 23,584 subscribers
Avg views / post
15.8
144 posts measured
Reaction rate
4.35%
reactions ÷ views · ER floor
Posts in window
144
of 144 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 2 of 144 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 26 September 2026
Posts held144 (29 August 2026 – 26 September 2026)
Views total2,281
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 00:50 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

Photos
≈6,140
Videos
≈6,130
Links
≈295

Lifetime counters from Telegram’s own channel header, read 27 September 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.

Video runtime
2h 15m
Average length
1m 30s

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

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤150.0%
🤩150.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 2 of the 144 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

26 Sept 2026, 17:44 UTC32 viewsread 27 September 2026
Video

#越南吃瓜 # 打飞机 胡志明3郡某个美甲店 女朋友的朋友被吓得不轻 刚刚发生的事情。 关注吃瓜频道➡️ @ggyifan88 投稿:@qsjt_7

26 Sept 2026, 15:04 UTC42 views1 reactionsread 27 September 2026
Photo

#潘娇娇 #秀人网巨乳网红 秀人网巨乳网红 潘娇娇 自慰摇奶福利 湿润蜜穴一览无余 绝对是罕见的人间极品 看视频🌏 关注吃瓜频道➡️ @ggyifan88 投稿:@qsjt_7

🤩1

26 Sept 2026, 14:36 UTC41 viewsread 27 September 2026
Photo

戚薇在时尚芭莎红毯穿的3D打印水花裙。出场方式真特别,被工作人员拿手推车推上场。 关注吃瓜频道➡️ @ggyifan88 投稿:@qsjt_7

26 Sept 2026, 14:35 UTC47 viewsread 27 September 2026
Photo

#女网友 #面基 #约p 这样就🉐吃了?! 关注吃瓜频道➡️ @ggyifan88 投稿:@qsjt_7

26 Sept 2026, 14:28 UTC34 viewsread 27 September 2026
Video

幸亏有个好老婆,不然大概率要被关进去 关注吃瓜频道➡️ @ggyifan88 投稿:@qsjt_7

26 Sept 2026, 13:53 UTC33 viewsread 27 September 2026
Photo

#仙女美丽时刻 具体细节在这里 越南女子金骗去中国男人7万, 判刑7年 关注吃瓜频道➡️ @ggyifan88 投稿:@qsjt_7

26 Sept 2026, 12:50 UTC36 viewsread 27 September 2026
Video

刘欢励志金曲《从头再来》鼓励每个为梦想迷茫的人。 关注吃瓜频道➡️ @ggyifan88 投稿:@qsjt_7

26 Sept 2026, 12:42 UTC36 viewsread 27 September 2026
Photo

傍晚,广州-人和镇 #摩托 #车祸 希望没有人员伤亡 关注吃瓜频道➡️ @ggyifan88 投稿:@qsjt_7

6 Sept 2026, 15:54 UTC31 viewsread 7 September 2026
Photo

#晓璇 #ins极品高颜博主 ins极品高颜博主 晓璇 与前男友性爱视频流出 大尺度调教猛干 女神形象彻底崩塌 看视频🌏 传送门 关注吃瓜频道➡️ @ggyifan88 投稿:@qsjt_7

6 Sept 2026, 15:49 UTC33 viewsread 7 September 2026
Video

保养一下嫩腿 无不良引导 #恋足 关注吃瓜频道➡️ @ggyifan88 投稿:@qsjt_7

6 Sept 2026, 15:20 UTC31 viewsread 7 September 2026
Photo

#女性力量 #打男人 男子被女友家暴,遭遇分手困难!无奈报警说被女友盗窃和猥亵 #家暴 关注吃瓜频道➡️ @ggyifan88 投稿:@qsjt_7

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 1 registered channel — 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.

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

“东南亚/吃瓜/搞笑曝光” (@ggyifan88), 23,584 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ggyifan88.

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.