Telegram RegisterThe public register of Telegram

Channel

奇趣百科🅥全网精选 吃瓜 搞笑 热门 头条

@t66u6

2 usernames

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

30,824subscribers

-541 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001176953047
TypeChannel
Usernames@chiguazhongxin4 @t66u6
Description吃瓜中心 欢迎加入智慧天下联盟 天下社区:华人求助贴 永久免费 全网覆盖 广告招商/商务合作: @mengbao99 广告招商/商务合作: @yoozb 天下联盟导航: @Txtot #覆盖全球 #柬埔寨 #商务合作 #西港 #金边 #缅北 #迪拜 #老挝特区 #金三角 #菲律宾 #越南 #泰国 #曝光 #悬赏 #通缉 #置顶广告 #飞机万人群搭建 #频道群组采集强拉活粉 #大量机器人 #出码 #会所 #人事代理 #号商 #商家
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held13
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/t66u6

Growth

30,82431,36531,094.57 August 2026 — 31,365 subscribers7 August 2026 — 31,341 subscribers7 August 2026 — 31,329 subscribers8 August 2026 — 31,257 subscribers8 August 2026 — 31,252 subscribers9 August 2026 — 31,117 subscribers9 August 2026 — 31,117 subscribers10 August 2026 — 30,994 subscribers10 August 2026 — 30,993 subscribers11 August 2026 — 30,981 subscribers11 August 2026 — 30,981 subscribers12 August 2026 — 30,865 subscribers12 August 2026 — 30,824 subscribers7 August 202612 August 2026
13 measurements spanning 6 days, net -541. 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 30,743–31,446 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 23:0730,824-41
12 Aug 2026, 19:3330,865-116
11 Aug 2026, 20:1630,981no change
11 Aug 2026, 17:4630,981-12
10 Aug 2026, 20:4630,993-1
10 Aug 2026, 17:1130,994-123
9 Aug 2026, 18:1431,117no change
9 Aug 2026, 18:1131,117-135
8 Aug 2026, 21:1831,252-5
8 Aug 2026, 18:5631,257-72
7 Aug 2026, 21:1831,329-12
7 Aug 2026, 16:3731,341-24
7 Aug 2026, 09:1631,365first reading

Engagement

191 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 19 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.042%
avg views ÷ 30,824 subscribers
Avg views / post
12.9
186 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
191
of 191 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 13 August 2026
Posts held191 (7 August 202613 August 2026)
Views total2,397
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 10:10 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
20,600
Videos
28,700
Links
23,500

Lifetime counters from Telegram’s own channel header, read 13 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
1h 47m
Average length
48s

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

13 Aug 2026, 09:46 UTC10 viewsread 13 August 2026
Photo

郭德纲演出中即兴改编红歌遭举报,武汉市文旅局立案调查 8月 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

13 Aug 2026, 09:46 UTC11 viewsread 13 August 2026
Photo

长鑫科技市值登顶,超越腾讯,成为中国市值最大的上市公司。 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

13 Aug 2026, 09:46 UTC5 viewsread 13 August 2026
Photo

苹果CEO库克悼念朱镕基 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

13 Aug 2026, 09:46 UTC5 viewsread 13 August 2026
Photo

三位总理同框 2002年黄河花园口,一张照片同时出现朱镕基、温家宝和时任河南省长李克强,三个人后来先后担任中国总理。二十多年后再看,这张照片突然有了另一层意味。朱镕基去世后,《纽约时报》《华尔街日报》《金融时报》都在强调他推动市场化、WTO和全球化的遗产。 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

13 Aug 2026, 09:31 UTC12 viewsread 13 August 2026
Photo

水龙头🚰 不出水谁会修 ? 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

13 Aug 2026, 09:31 UTC12 viewsread 13 August 2026
Photo

华人女孩在巴厘岛旅游时被两个意大利男生亲,她非常的开心且享受。她最后回应评论区的有些人很搞笑,一边攻击我,一边又有人私信问“我为什么亲的不是我?” #仙女美丽时刻 #亚洲马桶 #easygirl 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

13 Aug 2026, 09:31 UTC11 viewsread 13 August 2026
Video

下次拿警棍拿电击枪驱赶吧 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

12 Aug 2026, 19:16 UTC11 viewsread 12 August 2026
Video

一键变装 #ai 有点像 杨幂 ? https://t.me/+jVtey_K9_9gxYzI 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

12 Aug 2026, 19:01 UTC12 viewsread 12 August 2026
Photo

8月 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

12 Aug 2026, 18:46 UTC10 viewsread 12 August 2026
Video

集美才艺大秀 🍉 吞火 🔥 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

12 Aug 2026, 18:46 UTC10 viewsread 12 August 2026
Video

精神小妹打架,打了女的之后被打 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

12 Aug 2026, 18:01 UTC17 viewsread 12 August 2026
Video

泰国,芭提雅步行街,美女杀敌一千自损八百,大哥做的牛掰啊 👇 飞机吃瓜尽在吃瓜中心 ↓ https://t.me/t66u6 ✅投稿澄清:@yoozb

Showing the 12 most recent of 191 posts we hold for @t66u6. 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 — 679,304 of 1,169,250entries 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.

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

“奇趣百科🅥全网精选 吃瓜 搞笑 热门 头条” (@t66u6), 30,824 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/t66u6.

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.