🔥TeleTop 频道推荐 📢网红短剧|热播短剧|最新短剧 📢欧博官网 亚星官网 欧博代理 亚星代理 📢TGRSS 总频道🔥Telegram ... 📢币盘盘口丨外汇盘口丨外卖盘口丨海外盘口招... 📢4K AI Wallpapers 📢皇冠体育 皇冠娱乐 皇冠官网 皇冠代理 📢世界杯|五大联赛|足球推单 📢国外ip 海外ip 静态ip 动态ip ... 📢Telegram优质资源导航 📢华人大事件 新闻曝光 东南亚大事件 💎广告推荐 📢⚽️爱博体育-佣金55%-玩家首存即升V... 📢182体育综合平台,电子,棋牌,百家乐,... 📢💎85.CC电子百家乐0审核包出款支持... 🔍互推公示 🪧流量互推说明

Channel
瓜次元 Ι 吃瓜日常🍉
@Guaciyuan
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
21subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003959428406 |
|---|---|
| Type | Channel |
| Username | @Guaciyuan |
| Created | Between 1 April 2026 and 26 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Guaciyuan |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 21:18 | 21 | +2 |
| 11 Aug 2026, 16:31 | 19 | no change |
| 6 Aug 2026, 19:51 | 19 | first reading |
Engagement
19 posts held, back to 26 June 2026 — the 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
- 104.8%
- avg views ÷ 21 subscribers
- Avg views / post
- 22.0
- 5 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 5
- of 19 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.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 19 (26 June 2026 – 11 August 2026) |
| Views total | 110 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 16:31 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
- Video runtime
- 3m 26s
- Average length
- 34s
Measured directly from 6 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
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
https://t.me/ShunWangcc
🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道
按摩这门手艺,有时间确实可以学一下
兄弟们晚安💤
湿透了
Showing the 12 most recent of 19 posts we hold for @Guaciyuan. 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 — 796,182 of 1,345,403entries 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 8 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.
Named by
Channels on the register whose posts name this channel's handle.
@tgrss · 3,0242 posts🎪性瘾反差婊
@binguo16888 · 1,8311 post【情报局查档】老牌查档/司法/定位/流水/开同/户籍👨✈️
@dvadwasfasf · 8,1321 post【一手】谷歌邮箱💋 推特账号💋ins账号 fb账号
@fjh1324 · 8,3971 post皇冠娱乐 皇冠平台 皇冠下注 皇冠投注
@jdnhhd · 6881 post2026世界杯 世界杯赛事 世界杯投注 世界杯买球 足球世界杯 足球投注
@waiweizuqiu11 · 3751 post热点事件
@xw966 · 9761 postTelegram数字生活指南
@Youzhigongxu00 · 6,7041 post
Names
Channels on the register whose handles appear in this channel's posts.
@TeleTopOrg · 33,0798 posts爱博体育官方频道
@aibonbcom · 15,9781 post华人大事件 新闻曝光 东南亚大事件
@BG_133 · 9571 postTelegram优质资源导航
@Boling666666 · 3,2971 post4K AI Wallpapers
@DarkAIBG_4K · 2961 post世界杯|五大联赛|足球推单
@SHCTTY · 34,5621 post顺网加速官方频道
@ShunWangcc · 4231 post国外ip 海外ip 静态ip 动态ip socks5代理 http代理
@socks5_1 · 1531 postTGRSS 总频道🔥Telegram 最全能的内容矩阵!
@tgrss · 3,0241 post皇冠体育 皇冠娱乐 皇冠官网 皇冠代理
@TKqunfa_3 · 3901 post🔥 182体育 福利频道(PG电子)
@vip182ty · 10,4031 post
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“瓜次元 Ι 吃瓜日常🍉” (@Guaciyuan), 21 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Guaciyuan.
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.