Telegram RegisterThe public register of Telegram
Telegram profile photo for 全网吃瓜🍉

Channel

全网吃瓜🍉

@aichiguaba

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

252,553subscribers

+23 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001819259766
TypeChannel
Username@aichiguaba
Description吃瓜 广告投稿机器人👉 @BGTGOBOT
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/aichiguaba

Topic

Sports — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 72% 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

210,876260,514235,6957 August 2026 — 252,530 subscribers7 August 2026 — 252,489 subscribers8 August 2026 — 252,285 subscribers9 August 2026 — 251,962 subscribers10 August 2026 — 251,756 subscribers12 August 2026 — 231,980 subscribers13 August 2026 — 210,876 subscribers14 August 2026 — 260,514 subscribers16 August 2026 — 260,155 subscribers17 August 2026 — 259,775 subscribers18 August 2026 — 259,083 subscribers19 August 2026 — 258,804 subscribers20 August 2026 — 258,275 subscribers22 August 2026 — 256,946 subscribers23 August 2026 — 256,608 subscribers25 August 2026 — 256,354 subscribers26 August 2026 — 256,046 subscribers27 August 2026 — 255,942 subscribers28 August 2026 — 255,789 subscribers29 August 2026 — 255,421 subscribers30 August 2026 — 255,102 subscribers31 August 2026 — 254,839 subscribers1 September 2026 — 254,485 subscribers2 September 2026 — 254,122 subscribers3 September 2026 — 253,661 subscribers5 September 2026 — 253,377 subscribers9 September 2026 — 252,553 subscribers252,5537 August 20269 September 2026
27 measurements spanning 33 days, net +23. 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 203,430–267,960 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
9 Sept 2026, 03:17252,553-824
5 Sept 2026, 20:17253,377-284
3 Sept 2026, 15:38253,661-461
2 Sept 2026, 07:38254,122-363
1 Sept 2026, 06:46254,485-354
31 Aug 2026, 04:27254,839-263
30 Aug 2026, 04:55255,102-319
29 Aug 2026, 04:07255,421-368
28 Aug 2026, 04:03255,789-153
27 Aug 2026, 01:38255,942-104
26 Aug 2026, 01:14256,046-308
25 Aug 2026, 00:33256,354-254
23 Aug 2026, 14:35256,608-338
22 Aug 2026, 00:06256,946-1,329
20 Aug 2026, 20:27258,275-529
19 Aug 2026, 18:47258,804-279
18 Aug 2026, 16:15259,083-692
17 Aug 2026, 12:47259,775-380
16 Aug 2026, 07:34260,155-359
14 Aug 2026, 16:24260,514first reading

Engagement

583 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 72 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.34%
avg views ÷ 252,553 subscribers
Avg views / post
859
506 posts measured
Reaction rate
0.226%
reactions ÷ views · ER floor
Posts in window
506
of 583 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 341 of 506 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 9 September 2026
Posts held583 (7 August 20269 September 2026)
Views total434,716
Reactions total704
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Sept 2026, 03:19 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
60,100
Videos
107,000
Links
9,550

Lifetime counters from Telegram’s own channel header, read 10 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
5h 56m
Average length
50s

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

766 reactions across 344 posts, in 23 distinct kinds. The most used accounts for 40.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍31140.6%
27836.3%
😁405.22%
💩283.66%
🍌243.13%
🤡162.09%
🤮111.44%
🌭91.17%
😈91.17%
😍60.783%
🙏60.783%
🕊40.522%
🖕40.522%
😱40.522%
🤬40.522%
🌚30.392%
👏20.261%
🤓20.261%
🐳10.131%
👎10.131%
3 further kinds30.392%

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

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

9 Sept 2026, 13:20 UTC≈1,210 views2 reactionsread 10 September 2026
Photo

小米 澎程 N90 Max 探索版 移动炮房 #补充 #车震 豪车 ? 车内空间也不错 直接可以睡觉了

1😁1

9 Sept 2026, 13:19 UTC≈1,090 viewsread 10 September 2026
Photo

9月7日,一网友发帖称,自己玩《无畏契约》时为了押韵朋友的话说了一句“我是习近平”,账号被封禁十年,直到2036年才能解封。 该网友写道: “我为了押韵朋友的话说了一句我是刁迈乎。秒禁言呀。。。” “因为说了他大名就给我封10年。”

9 Sept 2026, 13:18 UTC≈1,020 views1 reactionsread 10 September 2026
Video

9月7日,广东湛江,多名装修务工人员因遭欠薪,前往中铁北京工程局集团广湛铁路房建三标项目经理部外拉横幅维权。

1

9 Sept 2026, 13:17 UTC950 views0 reactionsread 10 September 2026
Photo

深圳中学大鹏学校防欺凌求助信箱事件后续: 校方回应称,当时老师已收到同学直接反映,已经处理了相关事情。校方还说,学校有定期清理信件,有整改。 面对校方回应,网友似乎并不买账,有人评论说:“已经处理了,指求救的学生。” 9月6日,有网友发现,在深圳中学大鹏学校设立的“防霸凌信箱”内部,有两封早已破损、发黄的求助信,且信箱内部积积灰严重。该网友质疑“摆设吗?”。 信件内容显示,写信学生向校长反映某同学长期存在打人、偷拿他人财物等霸凌行为,并请求校长“救救我们”。 评论区网友热议 “依旧形式主义” “咋给我垃圾桶改成这样了”

9 Sept 2026, 13:16 UTC834 viewsread 10 September 2026
Photo

“时代的发展也不是永远向前的。” 9月1日,广州太古汇方所因商场改造暂停营业。一网友在小红书发帖感叹“一个时代结束了”,并在评论区写道:“时代的发展也不是永远向前的。” 她回忆,刚入行时,领导会让她“放轻松”,没有催她内卷,而是给予学习、接手项目的机会。 2018年前后,自己买三百多元的雨伞也不在乎价格,如今网购却变得“扣扣搜搜”。 她写道:“不仅是因为方所,更因为整个时代的离去。” 评论区网友留言: “也好 原来大家都一样 不是只有我一个人下行” “以前再忙也一定是双休,加班有补贴和调休,年会大办特办,抽奖的奖品也大方,团建都是出国游。” “经济上行的时候,剪个头发四百块,剪得也确实好,现在消费降级几十块的,觉得也挺好” “以前读唔到书出来一样找到工作,现在读到书的出来都找不到工作。最有活力和最有钱的是退休那班人。” “以前以为经济上行是常态,现在才醒悟苟着活才是常态!”

8 Sept 2026, 14:39 UTC≈1,290 viewsread 9 September 2026
Photo

9月7日,刘德华调侃余承东,“买一个回去看看呗,不好用不要找我,找余总”,余承东在一旁尴尬地笑。华为这款新手机售价19999,这价格让品牌大使刘德华也咋舌,所以才会说出不好用不要找我这样怕挨骂的话。

8 Sept 2026, 14:38 UTC≈1,180 viewsread 9 September 2026
Photo

“CNN等外媒记者到达后震惊了” 9月6日,“8·26”中尼边境灾害发生第11天,中国外交部和国务院新闻办首次组织境外媒体进入西藏吉隆口岸受灾核心区。 CNN高级中国记者Simone McCarthy站在原五层联检大楼所在地报道,现场只剩钢筋、碎石和部分地基。 她表示,这是外国媒体首次获准进入中国一侧灾区。 随后,中国媒体以“CNN等外媒记者到达后震惊了”为题,重点强调外媒对救援工作的称赞; 但CNN原报道的标题则是:“ON THE GROUND IN CHINA'S WIPED-OUT BORDER ZONE, THE FATE OF HUNDREDS IS STILL UNKNOWN”(中国被抹去的边境地带,数百人的命运仍然未知)

8 Sept 2026, 14:36 UTC897 viewsread 9 September 2026
Photo

两名学生在BTS Siam发生冲突时被刺伤 两名泰国巴吞完科技学院的学生在周一上午于BTS Siam站与大约30名乌通塔威学生发生冲突时被刺伤。警方正在调查这次对峙是否通过社交媒体安排。 尽管有七名警察试图将他们分开,两群人仍于约7:45在车站三楼互相冲撞。 两名受伤学生,年龄分别为19岁和21岁,背部被刺伤。两人均被送往医院,目前情况稳定。 警方表示,这次冲突可能与上周附近天桥上的一场斗殴有关。警员正在查看闭路电视录像并询问目击者,以识别袭击者。

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

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

东南亚大事件
@bx666 · 473,715
#1
今日头条 曝光频道
@jrttbg · 164,642
#2
中文吃瓜中心沙雕日常 🍉
@chigua_a · 212,019
#3
吃瓜群众🍉
@chigua_e · 208,930
#4
吃瓜中心
@guawa9 · 89,993
#5
点亮曝光吧️💥
@baoguangba0 · 160,846
#6
缅北悬赏通缉令(吃瓜)❖盈丰娱乐冠名🅥
@DNYTJL3 · 102,544
#7
孟玺-东南亚悬赏通缉令
@mianbeitongjiling · 30,987
#8
🇵🇭菲行者:吃瓜中心
@feixingzhe_cgzx · 166,919
#9
吃瓜猎奇 幽默视频 搞笑段子
@ay2028 · 65,719
#10
中国悲剧档案官方频道
@newszg_official · 163,865
#11
电影频道【SOTV】
@cctv1 · 309,786
#12
telegram 高速飞机代理
@hgwzcd · 255,959
#13
㊙️吃瓜💘新闻热点
@chiguaxinwen · 456
#14
生活素材包装🔊
@AQzx_7 · 39,264
#15
全网曝光
@quanwangbaoguangb · 154,745
#16
吃瓜丨素材丨内涵段子丨搞笑视频
@chiguasucai · 12,119
#17
🍉吃瓜搞笑俱乐部🌚
@cggxhhh · 269,414
#18
东南亚挨打日记
@pyzcn · 222,248
#19
中文段子吃瓜中心
@chiguale8 · 21,515
#20
吃瓜搞笑
@guagua · 74,445
#21
吃瓜新闻
@chiguaxinwen1 · 21,910
#22
吃瓜群众/内涵段子/搞笑视频
@chigua186 · 19,731
#23
DJ音乐网
@AQzx_3 · 94,245
#24
海外大事件(猎奇-吃瓜)
@aa144 · 35,251
#25
缅甸新闻 ‖ 亚太新闻 ‖ 东南亚新闻
@cn789 · 20,286
#26
中文曝光吧 安危头条吃瓜(接广告合作)🫥
@ZLWBG · 96,883
#27
國際日報 东南亚吃瓜 墙外国内新闻
@GuoJiRiBao · 44,565
#28
搞笑视频 吃瓜群众 内涵段子 沙雕日常
@lsd62 · 25,279
#29
内涵搞笑🫥
@chiguahs · 110,192
#30
缅北园区吃瓜
@yuanqubot · 16,834
#31
吃瓜热门视频
@chigua278 · 40,787
#32
皮皮虾🦐搞笑吃瓜
@pipixia · 12,385
#33
🍉东南亚の小视频「VIP」
@dnyxsp · 66,569
#34
搞笑视频/吃瓜群众/吃瓜中心
@gaoxiao88 · 22,511
#35
吃瓜群众【 猎奇】
@chiguadog · 154,340
#36
快来吃瓜
@renrenchigua · 68,206
#37
吃瓜段子 @FLLCG
@FLLCG · 40,252
#38
吃瓜老祖
@chigualaozu · 19,899
#39
【吃瓜🍉&搞笑】
@GQSP9 · 110,810
#40
吃瓜研究所
@chigua_office · 3,968
#41
吃瓜视频战争头条新闻
@xy91d · 13,333
#42
东南亚大事件-聚焦时事
@pp854 · 69,229
#43
吴哥时报
@wgsb · 211,778 (as read 14 August 2026)
#44
搞笑视频
@MoiFunVideo · 6,291
#45
Trading Pit Signal (OFFICIAL)
@tradingpitsignal01 · 18,265
#46
1000pips builder fx signal
@pipsbuildersignal01 · 18,888
#47
خبر فوری
@khabar_furei · 2,622,048
#48
خبر ویژه
@khabarevijh · 355,438
#49
Alex Gold Trader
@Alex_goldtraderr · 21,632
#50
Pumpcoinbets💰📈 NFT & Crypto Gems 💎
@pumpcoinbets · 998,208
#51

Read from Telegram’s recommendation API, most recently 14 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

吃瓜🍉|搞笑🥸|软色情🥵|树洞投稿📮
@onlychigua · 199,424
Telegram ranks this channel #40 of 48 here — alongside 47 others — read 14 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“全网吃瓜🍉” (@aichiguaba), 252,553 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/aichiguaba.

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.