Telegram RegisterThe public register of Telegram

Channel

广州佛山花海集报告榜(重生)

@gzxsh8

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,050subscribers

+30 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003602028545
TypeChannel
Username@gzxsh8
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/gzxsh8

Growth

1,0201,1021,0616 August 2026 — 1,020 subscribers7 August 2026 — 1,022 subscribers9 August 2026 — 1,102 subscribers13 August 2026 — 1,050 subscribers1,0506 August 202613 August 2026
4 measurements spanning 6 days, net +30. 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 1,008–1,114 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 06:271,050-52
9 Aug 2026, 19:511,102+80
7 Aug 2026, 03:551,022+2
6 Aug 2026, 20:181,020first reading

Engagement

20 posts held, back to 29 July 2026the 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
11.3%
avg views ÷ 1,050 subscribers
Avg views / post
118
13 posts measured
Reaction rate
0.581%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 1 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (29 July 20266 August 2026)
Views total1,540
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 20:18 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.

Reaction mix

4 reactions across 1 post, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍250.0%
🤩125.0%
🥰125.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 1 of the 20 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 20 most recent posts we hold, published 29 July 2026 to 6 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.

Recent posts

6 Aug 2026, 08:50 UTC689 views4 reactionsread 6 August 2026

【报告群组】广佛花海集 【所在地区】#天河 【会所艺名】广州天河95高端私房菜 【技师翻牌】001 【联系方式】 @Xielin520 【验证留名】 航航 【验证日期】8.6 【会所价位】800 【技师几分】9 【身材几分】10 【推荐几分】9.5 【服务几分】10 【服务过程】 一出门身体都要融化了!好在欲望撑着,还是到了定位,上到房间,冷气迎面扑来那会,感觉什么都值了!我是比较急,就自己先洗了澡,不然黏糊糊的。结果洗好出来,就见着老师在床边等了,别说昂!暖色的灯光照在她脸上,看着真特么恬静,身上包臀裙贴着曲线,紧致又不失美感,胸前勒得都快挤出来啦!把我看来感觉了,她站起身就礼貌打招呼,鞠躬面前一抖一抖,贼有冲击!我很享受侧躺着被她毒龙舔,屁股对她的手贼敏感,她手冰冰凉凉却很有力,开始嘴里轻声说让我放松,屁股就被她掰开了,先是一股冷风抚过,接着就软绵绵的触感,从菊花直通脑壳,这种舒服是脸都有些火热的舒服!玩到

👍2🤩1🥰1

6 Aug 2026, 08:28 UTC32 viewsread 6 August 2026

@#会所报告模板 【报告群组】广佛花海集 【所在地区】 【会所艺名】 【技师翻牌】 【联系方式】 【验证留名】 【验证日期】 【会所价位】 【技师几分】 【身材几分】 【推荐几分】 【服务几分】 【服务过程】 打分标准: 7分及格,8分漂亮,9分优质,10分无脑冲 ⚠️支持匿名报告 报告提交给👉🏻 识花君 👈🏻处 ,并出示确认可添加的联系方式聊天等截图,交流群: https://t.me/Gzxshyyds01

5 Aug 2026, 09:26 UTC60 viewsread 6 August 2026
Photo

💐💐💐开奖了💐💐💐 禅城涵涵半价抽奖活动 开奖了! 本期总参与人数: 152 1- 保安大队长 获得:P半价 2- 摩卡 获得:P100优惠券 3- 比卡超 【上岸爆】 获得:P100优惠券 4- 炸号兜.[子浩军团] 获得:P100优惠券 5- 奥特曼 获得:P100优惠券 6- 烈火鸫上岸版 获得:P100优惠券 7- 瘾🐍 |6分钟爱恋 获得:PP200优惠券 8- BZ 获得:PP200优惠券 9- 老李 获得:PP200优惠券 10- Z EN 获得:PP200优惠券 11- 打茄伦(无订版) 获得:PP200优惠券 谨祝中奖用户大吉大利万事顺意

5 Aug 2026, 08:32 UTC49 viewsread 6 August 2026

【报告群组】广佛花海集 ❤️翻牌之人:山治 🌌翻牌老师:圆圆 🚏所在地区:天河 🏘️上课水费: 1400PP 📱联系方式: @yuanyuan8769 ⭐个人体验点评: 1️⃣类型:可爱嫩妹 2️⃣参考: 真人比照片更可爱,小巧玲珑 ---------硬件情况------------ ①【颜值年龄】8.5分,年轻可爱,脸型精致 ②【胸腰臀】小馒头,腰细,整体比例协调 ③【通道】紧致多水 ④【身材】小巧玲珑,好掌控 ⑤【皮肤】白嫩滑 —-----------软件情况-------------- ⑥【态度】9分,很乖很听话很温柔 ⑦【床技】8分,配合度高,动作认真 ⑧【情绪价值】9分,久别重逢依然温柔,体验舒服自然 出击体验: 一段时间没见圆圆了,有点想念她。今天天气不错,心情也顺,立马私信问了空档,约了PP课。 按时到达课室,遥控上楼。进门后圆圆还是那副乖巧的样子,笑着跟我打招呼,声音软软的。交完水费后直接去侍浴,她洗得挺仔细,过

5 Aug 2026, 08:28 UTC139 viewsread 6 August 2026

【报告群组】广佛花海集 ❤️翻牌之人:Ray 🌌翻牌老师:白云西西 🚏所在地区:嘉禾 🏘️上课水费: 500/p 📱联系方式: @DAD8806 ⭐个人体验点评:老师身材比较娇小,服务态度很好,很会聊天,要求基本都能满足,刚下海,很紧。照片原皮直出,所见即所得 1️⃣类型: 2️⃣参考: ---------硬件情况------------ ①【颜值年龄】25左右 ②【胸腰臀】比较瘦小 ③【通道】紧 ④【身材】身材比例不错,胸不大 ⑤【皮肤】正常皮肤 ------------软件情况-------------- ⑥【态度】很好 ⑦【床技】中上 ⑧【情绪价值】很好 出击体验: 看到老师挺久了,今天有空过来试了试,服务基本都给到位,聊天气氛也很好,老师刚下海,小小一个,比较紧。总体推荐 4️⃣优点:服务好,聊天气氛好,紧 5️⃣建议:身材9分,服务9.5分 推荐建议:整体 分【身材9分,服务9分】 ⚠️支持匿名报告 报告提交给👉🏻

4 Aug 2026, 19:02 UTCviews —

广州佛山花海集报告榜(重生) pinned «【报告群组】广佛花海集 ❤️翻牌之人: 🌌翻牌老师: 🚏所在地区: 🏘️上课水费: 📱联系方式: ⭐个人体验点评: 1️⃣类型: 2️⃣参考: ---------硬件情况------------ ①【颜值年龄】 ②【胸腰臀】 ③【通道】 ④【身材】 ⑤【皮肤】 ------------软件情况-------------- ⑥【态度】 ⑦【床技】 ⑧【情绪价值】 出击体验: 4️⃣优点: 5️⃣建议: 推荐建议:整体 分【身材9分,服务9分】 ⚠️支持匿名报告 报告提交给👉🏻 @gzxshzrbot…»

4 Aug 2026, 19:02 UTC64 viewsread 6 August 2026

【报告群组】广佛花海集 ❤️翻牌之人: 🌌翻牌老师: 🚏所在地区: 🏘️上课水费: 📱联系方式: ⭐个人体验点评: 1️⃣类型: 2️⃣参考: ---------硬件情况------------ ①【颜值年龄】 ②【胸腰臀】 ③【通道】 ④【身材】 ⑤【皮肤】 ------------软件情况-------------- ⑥【态度】 ⑦【床技】 ⑧【情绪价值】 出击体验: 4️⃣优点: 5️⃣建议: 推荐建议:整体 分【身材9分,服务9分】 ⚠️支持匿名报告 报告提交给👉🏻 @gzxshzrbot 👈🏻处 ,并出示确认可添加的联系方式聊天等截图,交流群: https://t.me/Gzxshyyds01

4 Aug 2026, 11:05 UTC77 viewsread 6 August 2026
Photo

🎰 越秀钰钰半价抽奖活动 📮 抽奖条件: 🎫 加入-钰钰的小窝 🎫 加入-(广州佛山)花海集 🅢 🎫 加入-广州佛山花海认证榜🅢 🎫 加入-广州佛山花海集报告榜(重生) 🎟️ 要求活动期间群内发言数 30 🍀 每10分中奖几率加1倍 ⤷在群中输入「喜+1」 🎁 奖品内容: P半价 × 1 💡 活动说明: 1. 自开奖后请在五日内兑奖 2. 炸号者中奖作废 3. 转赠需老师同意 4.不能有偿转让 5.兑奖必须写报告 6.兑奖联系: @YUYU_0112 📅 开奖日期:(UTC+8) 2026年08月07日 10时00分00秒

4 Aug 2026, 10:02 UTC57 viewsread 6 August 2026
Photo

🎰 越秀悠悠半价抽奖活动 📮 抽奖条件: 🎫 加入-悠悠的小屋 🎫 加入-(广州佛山)花海集 🅢 🎫 加入-广州佛山花海认证榜🅢 🎫 加入-广州佛山花海集报告榜(重生) 🎟️ 要求活动期间群内发言数 30 🍀 每10分中奖几率加1倍 ⤷在群中输入「喜+1」 🎁 奖品内容: P半价 × 1 💡 活动说明: 1. 自开奖后请在五日内兑奖 2. 炸号者中奖作废 3. 转赠需老师同意 4.不能有偿转让 5.兑奖必须写报告 6.兑奖联系: @YO_YO1120 📅 开奖日期:(UTC+8) 2026年08月09日 18时00分00秒

Showing the 12 most recent of 20 posts we hold for @gzxsh8. 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 — 699,508 of 1,478,351entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 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.

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

“广州佛山花海集报告榜(重生)” (@gzxsh8), 1,050 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/gzxsh8.

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.