Telegram RegisterThe public register of Telegram

Channel

吃瓜中心丨吃瓜群众丨 5G吃瓜丨搞笑视频

@gx135

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

336subscribers

+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-1001986819772
TypeChannel
Username@gx135
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/gx135

Growth

3367 Aug 2026, 03:02 — 336 subscribers7 Aug 2026, 22:30 — 336 subscribers7 Aug 2026, 03:027 Aug 2026, 22:30
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 335–337 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 22:30336no change
7 Aug 2026, 03:02336first reading

Engagement

11 posts held, back to 6 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.893%
avg views ÷ 336 subscribers
Avg views / post
3.0
11 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
11
of 11 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 6 August 2026
Posts held11 (6 August 20266 August 2026)
Views total33
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 03:02 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.

Recent posts

6 Aug 2026, 10:06 UTC3 viewsread 7 August 2026
Video

#美女 #合集 你老婆 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 10:06 UTC3 viewsread 7 August 2026
Video

小忙一会 👎 稍后更新 ... #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 10:06 UTC3 viewsread 7 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 😳更多福利尽在东方汇📴 传送门 ➡️🙄 东方汇娱乐简介🙄 😀😀😀😀😀😀😀😀😀😀

6 Aug 2026, 10:05 UTC3 viewsread 7 August 2026
Video

台湾 海巡署台中舰用水炮攻击大陆渔船 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 10:05 UTC3 viewsread 7 August 2026
Video

特朗普关于伊朗的讲话: 我更愿意与伊朗达成协议,因为我不想杀人。 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 10:05 UTC3 viewsread 7 August 2026
Photo

#对版萝莉? #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 10:05 UTC3 viewsread 7 August 2026
Video

这到底是什么神仙场面 现在的帅哥都这么拼了吗 感觉像穿越回了九零年代广东的老巷子 只不过这次位置颠倒啦 PS:这是哪条街,就单纯问问 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 10:05 UTC3 viewsread 7 August 2026
Video

10个看似令人羡慕的 #能力,其实竟是 #病? #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 10:05 UTC3 viewsread 7 August 2026
Video

眼里没有对 #美色 的 #渴望,只有对 #战神 的 #尊敬🤪 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 10:05 UTC3 viewsread 7 August 2026
Video

不愧是 #台湾省 政治系学生,资源就摆在眼前,资本雄厚 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 10:05 UTC3 viewsread 7 August 2026
Photo

开眼界啊,不是看评论区我都没明白 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

Showing the 11 most recent of 11 posts we hold for @gx135. 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 — 112,318 of 1,176,251entries 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 2 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 7 August 2026 — this entry's latest reading, not the date you are reading this.

“吃瓜中心丨吃瓜群众丨 5G吃瓜丨搞笑视频” (@gx135), 336 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/gx135.

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.