Channel
@ruoyao1314
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,452subscribers
-18 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002749038711 |
|---|---|
| Type | Channel |
| Username | @ruoyao1314 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 19 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 19 August 2026 |
| On Telegram | t.me/ruoyao1314 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Aug 2026, 03:47 | 3,452 | -169 |
| 16 Aug 2026, 02:08 | 3,621 | +146 |
| 12 Aug 2026, 20:53 | 3,475 | +5 |
| 12 Aug 2026, 02:01 | 3,470 | first reading |
13 posts held, back to 27 July 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 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. It is computed over the 4 of 12 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 13 (27 July 2026 – 11 August 2026) |
| Views total | 5,599 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 02:01 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.
Measured directly from 2 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.
4 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 4 of the 13 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 27 July 2026 to 11 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
致优秀老师： 为了打造更高效的本地服务生态 我们诚邀广州优质老师免费上榜 • 名额无忧： 优质老师尊享免费上榜机会 • 幸运回馈： 参与社群专属免费抽奖活动 • 成长赋能： 群内核心渠道流量深度倾斜 免费上榜 达标优质老师 抽奖现金/半价费我们出 💰💰💰💰💰💰💰💰 期待您的加入，携手合作，共赢未来。 联系 @Yyyang86 https://t.me/guangzhouyangyang
Signed (天河)若瑶
哥哥快来抓大白兔了。
Signed (天河)若瑶
Video, posted without a caption
Signed (天河)若瑶
羊城晚报和你共同选择广州精品 群聊 https://t.me/+c1YbH0ENgcExNzhl
Signed (天河)若瑶
宝宝们可以约课了，身体检查已做。
Signed (天河)若瑶
🎉 桃花 若瑶优惠卷奶茶活动 🎁 奖品清单 • p优惠劵 × 10 • pp200优惠劵 × 5 • 28奶茶 × 2 🛡️ 参与条件 • 加入 广州佛山修车桃花污 • 加入 广州佛山修车桃花榜 • 加入 广州佛山修车桃花会所榜 • 加入 广州佛山桃花污优选推荐 • 加入 桃花备胎（退群拉黑） • 加入 天河若🌸瑶小仙女🦋重建版 • 必须设置用户名 🔮 祝福加持 • 祝福消耗：10桃花蜜 • 祝福上限：200次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-08-12 22:00:00 📜 抽奖说明 ❶ 自开奖时间起 7 天内兑奖 联系：@Zzzyao ❷ 炸号中奖作废！抽中半价拉黑30天，按要求提交报告后解除： @PeachBGbot ❸ 连续多次半价未出击，或未按要求提交报告永久拉黑抽奖 ❹ 中奖减扣：不减扣 ✔️ 转让需经老师本人同意，任何形式买卖…
❤1
Signed Saber
🎉 广佛鹊桥修车群天河若瑶优惠劵奶茶活动 🎁 奖品清单 • P-100优惠劵 × 10 • PP减200优惠劵 × 5 • 18元奶茶红包 × 2 🛡️ 参与条件 • 加入 广佛鹊桥修车群 • 加入 广佛鹊桥公开榜 • 加入 广佛鹊桥报告 • 加入 广佛鹊桥甄选 • 加入 天河若🌸瑶小仙女🦋重建版 • 需持有喜鹊分： 20 • 参加抽奖后需在 广佛鹊桥修车群 内发言20次 └ 群内发送“抽奖进度”查看完成度（每日限5次） • 必须设置用户名 🔮 祝福加持 • 祝福消耗：20喜鹊分 • 祝福上限：30次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-08-14 12:00:00 📜 抽奖说明 兑奖联系: @Zzzyao 1.半价优惠券有效期为7天，中奖者需要七天内出击并且提交报告，不是老师的原因超时不出击交报告永久拉黑抽奖！ 2.禁止买卖优惠券，发现封禁处理 …
Signed Saber
昔人已乘黄鹤去，此地空余黄鹤楼。
Signed (天河)若瑶
谢谢宝宝 还没开课 就给我介绍朋友啦 有被宝宝惦念的感觉真好 😘😘
❤2
Signed (天河)若瑶
嘻嘻！武汉的小乌龟🐢还是很好吃哒 😁😁
❤1
Signed (天河)若瑶
天河若🌸瑶小仙女🦋重建版 pinned «✨ 命运揭晓时刻 ✨ 广州鹊桥修车群天河若瑶优惠劵红包活动 开奖了 抽奖人数：17，发言达标人数：15，抽奖号数：86 1. 幽默呐【祝福22次】 中得：P-100优惠劵 2. 小嘟嘟的【祝福2次】 中得：P-100优惠劵 3. 爱舔白虎逼 也爱嗦玉足（币圈跟逼圈不算跨界，币圈赚钱逼圈花，一分别想带回家） 中得：P-100优惠劵 4. 🥛奶子很大树先生（赏你一发洗面奶暴打全套退骚针）【祝福1次】 中得：P-100优惠劵 5. E300L 中得：P-100优惠劵 6. 爱吃不吃香菜【祝福35次】 中得：P…»
✨ 命运揭晓时刻 ✨ 广州鹊桥修车群天河若瑶优惠劵红包活动 开奖了 抽奖人数：17，发言达标人数：15，抽奖号数：86 1. 幽默呐【祝福22次】 中得：P-100优惠劵 2. 小嘟嘟的【祝福2次】 中得：P-100优惠劵 3. 爱舔白虎逼 也爱嗦玉足（币圈跟逼圈不算跨界，币圈赚钱逼圈花，一分别想带回家） 中得：P-100优惠劵 4. 🥛奶子很大树先生（赏你一发洗面奶暴打全套退骚针）【祝福1次】 中得：P-100优惠劵 5. E300L 中得：P-100优惠劵 6. 爱吃不吃香菜【祝福35次】 中得：P-100优惠劵 7. 椰椰清补凉🌱 中得：P-100优惠劵 8. AAA火箭批发马总【祝福1次】 中得：P-100优惠劵 9. 黏黏包【祝福1次】 中得：P-100优惠劵 10. jimmyD 中得：P-100优惠劵 11. 嗯。 中得：PP-200优惠劵 12. 逍遥～小芭蕉～（严肃深蹲版）【祝福5次】 中得：PP-200优…
Signed Saber
Showing the 12 most recent of 13 posts we hold for @ruoyao1314. 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 — 677,231 of 1,550,220entries 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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 19 August 2026 — this entry's latest reading, not the date you are reading this.
“天河若🌸瑶小仙女🦋重建版” (@ruoyao1314), 3,452 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/ruoyao1314.
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.