广州资源分布 资源区,视频区,低价区,高价区 报告真真假假,任何定金切勿超过100 如遇态度极差或货不对版,请在各评论区留言 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut

Channel
广州抽奖导航公示
@yuangbobo
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
16,153subscribers
+1,352 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002020229144 |
|---|---|
| Type | Channel |
| Username | @yuangbobo |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/yuangbobo |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 09:37 | 16,153 | +35 |
| 3 Sept 2026, 09:43 | 16,118 | -148 |
| 2 Sept 2026, 02:37 | 16,266 | +9 |
| 31 Aug 2026, 23:34 | 16,257 | +3 |
| 30 Aug 2026, 22:39 | 16,254 | +61 |
| 30 Aug 2026, 00:46 | 16,193 | +10 |
| 29 Aug 2026, 00:38 | 16,183 | +8 |
| 27 Aug 2026, 21:14 | 16,175 | +47 |
| 27 Aug 2026, 00:32 | 16,128 | -15 |
| 26 Aug 2026, 02:16 | 16,143 | +424 |
| 25 Aug 2026, 05:13 | 15,719 | +599 |
| 22 Aug 2026, 11:39 | 15,120 | +13 |
| 21 Aug 2026, 04:36 | 15,107 | +14 |
| 20 Aug 2026, 04:54 | 15,093 | +10 |
| 19 Aug 2026, 07:13 | 15,083 | +12 |
| 18 Aug 2026, 10:43 | 15,071 | +1 |
| 17 Aug 2026, 10:03 | 15,070 | +3 |
| 15 Aug 2026, 20:36 | 15,067 | +19 |
| 14 Aug 2026, 09:18 | 15,048 | +26 |
| 13 Aug 2026, 01:34 | 15,022 | first reading |
Engagement
155 posts held, back to 8 March 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 55 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.871%
- avg views ÷ 16,153 subscribers
- Avg views / post
- 141
- 96 posts measured
- Reaction rate
- 0.308%
- reactions ÷ views · ER floor
- Posts in window
- 119
- of 155 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. It is computed over the 11 of 96 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 155 (8 March 2025 – 3 September 2026) |
| Views total | 13,510 |
| Reactions total | 11 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:09 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
- 19s
- Average length
- 19s
Measured directly from 1 video 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.
Reaction mix
25 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 76.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 19 | 76.0% | |
| 🎉 | 3 | 12.0% | |
| 🔥 | 3 | 12.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 17 of the 155 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 155 most recent posts we hold, published 8 March 2025 to 3 September 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.
Recent posts
广州资源分布 资源区,视频区,低价区,高价区 报告真真假假,任何定金切勿超过100 如遇态度极差或货不对版,请在各评论区留言 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut
广州资源分布 资源区,视频区,低价区,高价区 报告真真假假,任何定金切勿超过100 如遇态度极差或货不对版,请在各评论区留言 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut
广州资源分布 资源区,视频区,低价区,高价区 报告真真假假,任何定金切勿超过100 如遇态度极差或货不对版,请在各评论区留言 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut
广州抽奖导航公示 pinned a photo
💐💐💐开奖了💐💐💐 贝拉口令红包优惠券,兑奖联系贝拉 @beila2001 开奖了! 本期总参与人数: 5125 1- Neptu 获得:18奶茶红包 2- 肥仔烧鹅 获得:18奶茶红包 3- WiFi密码 获得:100优惠券 4- 钢铁雄心 获得:100优惠券 5- 入微身法 获得:100优惠券 6- 一直在你身边 获得:100优惠券 7- Cursor p 获得:100优惠券 8- 不会很晚 获得:100优惠券 9- 划船不靠浆全凭一个浪 获得:100优惠券 10- 猫王 获得:100优惠券 11- 老三的老二老大了 获得:100优惠券 12- 我咔咔一顿挖 获得:100优惠券 谨祝中奖用户大吉大利万事顺意
广州资源分布 资源区,视频区,低价区,高价区 报告真真假假,任何定金切勿超过100 如遇态度极差或货不对版,请在各评论区留言 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut
广州资源分布 资源区,视频区,低价区,高价区 报告真真假假,任何定金切勿超过100 如遇态度极差或货不对版,请在各评论区留言 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut
广州资源分布 资源区,视频区,低价区,高价区 报告真真假假,任何定金切勿超过100 如遇态度极差或货不对版,请在各评论区留言 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut
广州资源分布 资源区,视频区,低价区,高价区 报告真真假假,任何定金切勿超过100 如遇态度极差或货不对版,请在各评论区留言 广州资源榜 https://t.me/miuort 广州视频榜 https://t.me/puoeuzk 广州高价榜 800到900以上 https://t.me/mdhtuzoso 广州低价榜 400到800 https://t.me/HYHgut
广州抽奖导航公示 pinned a photo
💐💐💐开奖了💐💐💐 椰椰口令红包优惠券,兑奖联系椰椰 @yeye03520 开奖了! 本期总参与人数: 4119 1- 😊😊 获得:18奶茶红包 2- 转眼熙 获得:18奶茶红包 3- 砍价王Billy哥 获得:100通用优惠券 4- 刘域名 获得:100通用优惠券 5- 心灵的窗户 获得:100通用优惠券 6- 伏地魔的自我修养 获得:100通用优惠券 7- 美食家王刚 获得:100通用优惠券 8- 笑看人生 获得:100通用优惠券 谨祝中奖用户大吉大利万事顺意
Showing the 12 most recent of 155 posts we hold for @yuangbobo. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 12 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.
@mdhtuzoso · 16,6138 posts广州资源中转站
@RTiiuct · 18,4388 posts广州低价榜
@HYHgut · 14,3326 posts广州资源榜
@miuort · 51,5666 posts佛山资源榜
@Heutmy · 19,7392 posts广州潮流一线报告
@HigKut · 8,4182 posts广州高颜值榜
@mudess2362 · 4,6092 posts广州视频榜
@puoeuzk · 27,1312 posts广州紫瑶宫报告
@yzzxin666 · 14,4822 posts🌸为国争光🇯🇵
@husd866 · 3,8991 post茉莉😍个人开👄莞式水床🛏️
@moli888aa · 7,0191 post请把你的口水射我嘴里
@yjjy_3 · 7491 post
Names
Channels on the register whose handles appear in this channel's posts.
@miuort · 51,566118 posts广州低价榜
@HYHgut · 14,33283 posts广州高价榜
@mdhtuzoso · 16,61379 posts广州视频榜
@puoeuzk · 27,13162 posts广州紫瑶宫🆑
@GHWYJM · 33,60542 posts广州紫瑶宫推广群
@YMUHKR · 37,50740 posts广州潮流一线
@GHKLROT · 31,47235 posts广州潮流推广群
@RGTREY · 34,90729 posts广州高颜值榜
@mudess2362 · 4,60912 posts广州资源中转站
@RTiiuct · 18,4386 posts广州紫瑶宫报告
@yzzxin666 · 14,4826 posts广州潮流一线报告
@HigKut · 8,4184 posts广州时代推广群
@GZCLYX · 20,0623 posts红颜的朋友圈
@hongyan5210 · 5,0663 posts景甜小花园
@jingtian188 · 3,8053 posts广州天河暖暖
@nuan77788 · 1,3503 posts琪琪的小屋
@weopsg · 8,0983 posts元宝小花园
@yuanbao1236666 · 7,3163 posts贝拉 开课中~
@a2001bl · 3,9932 posts倩倩❤️(新人)首次下海
@gdhuuuui · 2,7742 posts广州SM女王 梦瑶
@mengyao202504 · 5,7122 posts浅浅🧍♀️ 兼职开🌹🌹🌹
@qianqian00110 · 2,2222 posts王菲花园
@wangfei5899 · 5,0412 posts珊珊❤️(新人首开)
@xyqq20 · 1,2722 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“广州抽奖导航公示” (@yuangbobo), 16,153 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/yuangbobo.
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.