Telegram RegisterThe public register of Telegram

Channel

内涵段子/吃瓜搞笑/每日瓜报/电报吃瓜

@chigua570

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

625subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001924235483
TypeChannel
Username@chigua570
Description传送门→🧧东方汇APP下载🧧 - https://43.226.40.188:3306/login/?&pid=52514011 传送门→🧧游戏上下分群🧧- https://t.me/+pSjLGTcVNHY4YTdl 传送门→🀄️东方汇娱乐🀄️ - https://t.me/DFHYL18
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/chigua570

Growth

6257 Aug 2026, 16:53 — 625 subscribers8 Aug 2026, 03:00 — 625 subscribers7 Aug 2026, 16:538 Aug 2026, 03:00
2 measurements taken within a single day. 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 624–626 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 03:00625no change
7 Aug 2026, 16:53625first reading

Engagement

10 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.48%
avg views ÷ 625 subscribers
Avg views / post
3.0
10 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
10
of 10 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held10 (7 August 20267 August 2026)
Views total30
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:00 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
63,800
Videos
92,600
Links
86,600

Lifetime counters from Telegram’s own channel header, read 8 August 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
8m 48s
Average length
59s

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

Recent posts

7 Aug 2026, 14:41 UTC3 viewsread 8 August 2026
Video

有包皮的鸡巴不吃 太硬的也不吃 #科普 #口交 吃鸡巴的怪兽 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

7 Aug 2026, 14:41 UTC3 viewsread 8 August 2026
Photo

送到我房来 #美女 #合集 👀 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

7 Aug 2026, 14:40 UTC3 viewsread 8 August 2026
Video

🤣😂🤣😁东方汇国际娱乐赌场🙄 🤣😂🤣😁有国家政府批准合法合规注册经营许可证的大型国际赌场🙄 ➡️首存赠送🤨♠️♠️🎲,最高🕉♐️♐️♐️元 🎲🎲🎲存款有礼 ,返利 🎲🎲 现金存款有礼 最高可送🕉🎲 😳主营:AG视讯,PG电子,JDB电子,CQ9电子,PNG电子,PP电子,MG电子😳😳😳😳😳😳😳😳😳😳 ➡️充值提现支持:😟😉😞😊微信、支付宝、网银转账、🎲🎲🎲,多种支付快捷方式 😳官方游戏下载注册网址:https://web.877798.com:3306/login/?&pid=52514011 😳游戏上下分群:https://t.me/+pSjLGTcVNHY4YTdl 😳下载注册教程:https://t.me/DFHYL18/31 😳更多福利尽在东方汇📴 传送门 ➡️🙄 东方汇娱乐简介🙄 😀😀😀😀😀😀😀😀😀😀

7 Aug 2026, 14:40 UTC3 viewsread 8 August 2026
Video

喜欢吗 ? #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

7 Aug 2026, 14:40 UTC3 viewsread 8 August 2026
Video

秀恩爱 激怒 “单身狗” #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

7 Aug 2026, 14:40 UTC3 viewsread 8 August 2026
Video

某医院的牛逼派头保安 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

7 Aug 2026, 14:40 UTC3 viewsread 8 August 2026
Video

大爷是穷追不舍呀 #骑行 🚴‍♀️ #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

7 Aug 2026, 14:40 UTC3 viewsread 8 August 2026
Photo

菲律宾首都发现带有反华标语的弃置棺材 菲律宾外交部声明: 马尼拉,2026年8月7日——菲律宾外交部(DFA)不认可针对任何个人,包括外国公民或官员的暴力行为或暴力威胁。此类不负责任且不尊重他人的行为不可容忍。 菲律宾在维护言论自由权利的同时,外交部强调,这项权利并不包括暴力威胁,或危及他人安全与保障的行为。此类行为既不代表菲律宾政府处理对外关系的方式,也不代表菲律宾民众即使在涉及敏感政治议题时表达批评或不满的方式。 菲律宾政府重申,将认真履行其关于保障在菲外国公民和官员安全的职责与义务,其中包括根据《维也纳外交关系公约》和《维也纳领事关系公约》所承担的相关责任。 菲律宾外交部正在与执法部门密切协调。执法机构正在采取必要措施,以查明该事件的具体情况,并确定这一鲁莽行为的责任人。 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

7 Aug 2026, 14:40 UTC3 viewsread 8 August 2026
Video

带娃的妈就看着俩姐妹打 架,惊呆了我三观 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

7 Aug 2026, 14:40 UTC3 viewsread 8 August 2026
Photo

mina Mina #西村力 居住在韩国的日本前夜总会女招待网红MINA(Mina-chan)因被网暴拿脏钱追星和被偶像怼,直播自杀身亡 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

Showing the 10 most recent of 10 posts we hold for @chigua570. 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

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

“内涵段子/吃瓜搞笑/每日瓜报/电报吃瓜” (@chigua570), 625 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/chigua570.

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.