Telegram RegisterThe public register of Telegram

Channel

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

@chigua150

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

1,005subscribers

-19 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003319226883
TypeChannel
Username@chigua150
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/chigua150

Growth

1,0051,0241,014.57 August 2026 — 1,024 subscribers7 August 2026 — 1,017 subscribers10 August 2026 — 1,005 subscribers7 August 202610 August 2026
3 measurements spanning 4 days, net -19. 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 1,002–1,027 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 15:341,005-12
7 Aug 2026, 23:111,017-7
7 Aug 2026, 02:171,024first reading

Engagement

18 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
1.03%
avg views ÷ 1,005 subscribers
Avg views / post
10.3
18 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
18
of 18 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 held18 (6 August 20266 August 2026)
Views total186
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 02:17 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, 05:18 UTC11 viewsread 7 August 2026
Video

梦回唐朝——千斤小姐🤔 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 05:18 UTC11 viewsread 7 August 2026
Video

谁的责任? #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 05:18 UTC12 viewsread 7 August 2026
Video

小棉袄和皮夹克的区别! #小棉袄 #皮夹克 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 05:18 UTC13 viewsread 7 August 2026
Video

好糟糕的技术,教练都发脾气了😅 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 05:18 UTC16 viewsread 7 August 2026
Video

城府与我吧,我的孩子们 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 05:18 UTC17 viewsread 7 August 2026
Video

黑天鹅战斗力这么强啊😄😂 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 05:18 UTC11 viewsread 7 August 2026
Video

#车祸 一通乱撞 得陪多少钱 ? #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 05:18 UTC8 viewsread 7 August 2026
Video

天津街头,一辆正在执行急救任务、鸣笛示警的救护车正常行驶途中,一名乘坐轮椅的大妈刻意拦在车辆前方,迟迟不肯挪开,硬生生挡住了救护车前进路线。 现场医护人员不断劝说、示意对方及时避让,可大妈始终不为所动,长时间僵持堵塞生命通道。救护车每耽误一分钟,车上病患的危险就多一分,周围路人见状纷纷上前劝导,大妈最后才不情愿挪开位置,救护车得以继续赶路。 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 05:18 UTC8 viewsread 7 August 2026
Video

反着玩 ? #黑妹 屁股 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 05:18 UTC9 viewsread 7 August 2026
Video

巴基斯坦开伯尔-普什图省奇特拉尔地区突发洪水袭击,人们纷纷奔逃以求生。 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 05:18 UTC9 viewsread 7 August 2026
Video

天津街头,一辆正在执行急救任务、鸣笛示警的救护车正常行驶途中,一名乘坐轮椅的大妈刻意拦在车辆前方,迟迟不肯挪开,硬生生挡住了救护车前进路线。 现场医护人员不断劝说、示意对方及时避让,可大妈始终不为所动,长时间僵持堵塞生命通道。救护车每耽误一分钟,车上病患的危险就多一分,周围路人见状纷纷上前劝导,大妈最后才不情愿挪开位置,救护车得以继续赶路。#堵路 救护车 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

6 Aug 2026, 05:18 UTC11 viewsread 7 August 2026
Video

实拍南海黄岩岛海域,中方快艇合围侵闯的菲律宾快艇 #5G吃瓜 导航联盟🧭 😙 色情吃瓜 🙃 东南亚大事件 🇲🇲

Showing the 12 most recent of 18 posts we hold for @chigua150. 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 — 132,957 of 1,183,361entries 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 4 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.

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

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

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.