#频道互推 #相似推荐 ------------------------------ 📢 吃瓜娱乐资讯🔥 @SSBYQ 📢 东南亚吃瓜悬赏令 📢 东南亚全网曝光✨新闻✨头条✨悬赏 📢 东南亚DJ俱乐部 📢 东南亚悬赏曝光 📢 AI短剧动漫&真人 📢 东南亚时报|柬埔寨大事件|爆料|吃瓜 📢 东南亚曝光新闻[78.com独家冠名] 📢 同心骗子曝光反诈 📢 东南亚悬赏曝光 ------------------------------ 🤝 加入互推 · 获得曝光,赚邀请奖励

Channel
如意吃瓜🍉
@ruyicg
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Cite this entry
10,905subscribers
-22,242 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003451385641 |
|---|---|
| Type | Channel |
| Username | @ruyicg |
| Description | 欢迎加入-如意吃瓜🍉凌晨随机更新吃瓜 欢迎加入交流群聊频道 广告招商/商务合作 @x9500 |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 51 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/ruyicg |
Topic
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 01:16 | 10,905 | -206 |
| 5 Nov 2026, 21:56 | 11,111 | -21 |
| 4 Nov 2026, 22:06 | 11,132 | -20 |
| 3 Nov 2026, 18:38 | 11,152 | -13 |
| 2 Nov 2026, 15:30 | 11,165 | -45 |
| 1 Nov 2026, 15:46 | 11,210 | -117 |
| 31 Oct 2026, 16:16 | 11,327 | -133 |
| 30 Oct 2026, 18:27 | 11,460 | -103 |
| 29 Oct 2026, 20:44 | 11,563 | -293 |
| 28 Oct 2026, 23:51 | 11,856 | -253 |
| 28 Oct 2026, 01:30 | 12,109 | -79 |
| 26 Oct 2026, 23:16 | 12,188 | -119 |
| 25 Oct 2026, 22:47 | 12,307 | -232 |
| 24 Oct 2026, 19:40 | 12,539 | -130 |
| 23 Oct 2026, 20:27 | 12,669 | -946 |
| 22 Oct 2026, 19:30 | 13,615 | -450 |
| 21 Oct 2026, 13:59 | 14,065 | -83 |
| 20 Oct 2026, 09:16 | 14,148 | -161 |
| 19 Oct 2026, 06:27 | 14,309 | -108 |
| 18 Oct 2026, 04:01 | 14,417 | first reading |
Engagement
128 posts held, back to 16 August 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 58 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.034%
- avg views ÷ 10,905 subscribers
- Avg views / post
- 3.7
- 6 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 6
- of 128 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 7 November 2026 |
|---|---|
| Posts held | 128 (16 August 2026 – 7 November 2026) |
| Views total | 22 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 08:44 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
- ≈2,610
- Videos
- ≈4,590
- Links
- ≈78
Lifetime counters from Telegram’s own channel header, read 7 November 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 08m
- Average length
- 44s
Measured directly from 94 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
Telegram’s own ‘edited’ marker: 0 of 6 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
刷到一个频道后,通常还想找更多同类入口。 SOSO 精选频道会随机推荐一批已收录频道。 适合继续发现相近内容。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1003451385641_7745758283_channels_0f9e120f
在 Telegram 里找内容,先打开 SOSO 搜搜。 频道、群组、帖子、贴纸都可以搜;也可以从发现页继续浏览。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1003451385641_7745758283_a4b27755
SOSO 搜搜 把 Telegram 搜索和发现放在一个入口。 想继续找频道、群组、帖子或贴纸,直接输入关键词。 也可以从发现页继续浏览同类入口。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1003451385641_7745758283_soso_19b67f63
新群变化快,手动找很容易漏。 SOSO 会展示最近同步的新群入口,适合快速补充新的群组来源。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1003451385641_7745758283_newgroups_866296d1
频道适合看内容,群组更适合继续交流。 SOSO 可以直接找热门群组,也能按关键词搜同类圈子。 先打开看看当前推荐。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1003451385641_7745758283_groups_526b440b
SOSO 搜搜 把 Telegram 搜索和发现放在一个入口。 想继续找频道、群组、帖子或贴纸,直接输入关键词。 也可以从发现页继续浏览同类入口。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1003451385641_7745758283_soso_19b67f63
新群变化快,手动找很容易漏。 SOSO 会展示最近同步的新群入口,适合快速补充新的群组来源。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1003451385641_7745758283_newgroups_866296d1
频道适合看内容,群组更适合继续交流。 SOSO 可以直接找热门群组,也能按关键词搜同类圈子。 先打开看看当前推荐。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1003451385641_7745758283_groups_526b440b
刷到一个频道后,通常还想找更多同类入口。 SOSO 精选频道会随机推荐一批已收录频道。 适合继续发现相近内容。 🔗 本频道专属邀请链接 https://t.me/soso?start=autopromo_-1003451385641_7745758283_channels_0f9e120f
湖南岳阳华容步步高小区,家长说了几句说了男孩子玩手机,就要跳楼。最后答应买苹果手机才没跳!
是不是很多人约会,有带指甲刀的传统?
Showing the 12 most recent of 128 posts we hold for @ruyicg. 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.
Posts recorded as deleted after publishing
We recorded 5 posts on @ruyicg as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 6 September 2026
- Most recent seen missing
- 28 September 2026
- Median time before seen missing
- 8 days
- Seen missing in the last 30 days
- 0
Mentions
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“如意吃瓜🍉” (@ruyicg), 10,905 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/ruyicg.
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.