Telegram RegisterThe public register of Telegram
Telegram profile photo for 广州佛山修车大队LY之声

Channel

广州佛山修车大队LY之声

@shenzhenxxhya

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

23,982subscribers

-3,367 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002049077903
TypeChannel
Username@shenzhenxxhya
Description广佛联盟只收集入驻靠谱、优质、真实三大美女 上榜联系我 @xidongdong666 或者管理员帮你上榜也行,先上后付就可以 (群组列表有黑奴管理员) 选妃频道 https://t.me/shenzhenxxhya 群组 https://telegram.me/+iX5YQG_MsBUzOWU9
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/shenzhenxxhya

Topic

Other / unclassifiable — 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 70% 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 why it has no browse page of its own yet.

Growth

23,98227,35025,6667 August 2026 — 27,349 subscribers7 August 2026 — 27,349 subscribers7 August 2026 — 27,350 subscribers9 August 2026 — 27,117 subscribers10 August 2026 — 27,120 subscribers11 August 2026 — 27,118 subscribers12 August 2026 — 27,116 subscribers14 August 2026 — 27,106 subscribers15 August 2026 — 27,091 subscribers16 August 2026 — 27,081 subscribers17 August 2026 — 27,075 subscribers18 August 2026 — 27,065 subscribers20 August 2026 — 27,058 subscribers21 August 2026 — 27,051 subscribers22 August 2026 — 27,093 subscribers24 August 2026 — 27,158 subscribers25 August 2026 — 27,249 subscribers26 August 2026 — 27,272 subscribers27 August 2026 — 26,818 subscribers28 August 2026 — 26,084 subscribers29 August 2026 — 25,580 subscribers30 August 2026 — 25,448 subscribers31 August 2026 — 25,443 subscribers1 September 2026 — 25,480 subscribers2 September 2026 — 25,701 subscribers3 September 2026 — 25,479 subscribers5 September 2026 — 25,444 subscribers9 September 2026 — 25,463 subscribers11 September 2026 — 25,432 subscribers13 September 2026 — 25,464 subscribers15 September 2026 — 25,482 subscribers17 September 2026 — 25,734 subscribers25 September 2026 — 23,982 subscribers7 August 202625 September 2026
33 measurements spanning 49 days, net -3,367. 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 23,477–27,855 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
25 Sept 2026, 07:1623,982-1,752
17 Sept 2026, 05:0125,734+252
15 Sept 2026, 06:3825,482+18
13 Sept 2026, 14:5825,464+32
11 Sept 2026, 16:3625,432-31
9 Sept 2026, 01:1825,463+19
5 Sept 2026, 14:4225,444-35
3 Sept 2026, 18:3725,479-222
2 Sept 2026, 08:4425,701+221
1 Sept 2026, 07:3625,480+37
31 Aug 2026, 05:4125,443-5
30 Aug 2026, 09:1325,448-132
29 Aug 2026, 08:3825,580-504
28 Aug 2026, 09:3226,084-734
27 Aug 2026, 11:2626,818-454
26 Aug 2026, 09:5727,272+23
25 Aug 2026, 10:2127,249+91
24 Aug 2026, 07:5727,158+65
22 Aug 2026, 13:1527,093+42
21 Aug 2026, 02:0327,051first reading

Engagement

72 posts held, back to 5 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 65 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.87%
avg views ÷ 23,982 subscribers
Avg views / post
448
24 posts measured
Reaction rate
0.164%
reactions ÷ views · ER floor
Posts in window
24
of 72 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 7 of 24 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 28 September 2026
Posts held72 (5 August 2026 – 28 September 2026)
Views total10,746
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Sept 2026, 07:13 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
≈8,190
Videos
≈763
Links
≈1,280

Lifetime counters from Telegram’s own channel header, read 29 September 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
4m 04s
Average length
10s

Measured directly from 24 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.

Reaction mix

12 reactions across 10 posts, in 2 distinct kinds. The most used accounts for 91.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1191.7%
😨18.33%

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 10 of the 72 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 72 most recent posts we hold, published 5 August 2026 to 28 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

28 Sept 2026, 11:12 UTC159 viewsread 29 September 2026
Photo

📱#天河 #车陂 #喜悦水汇 🥰🥰🥰 打造天河高颜值94🐍💋💋💋专场 项目 💌 热舞💃互动 💌 激情🐍💋- 💌 上下真🈳全🍎 💌 真⁶₉互👅鲍,那里敏感👅那里 💌 👅🥚👅棍 💌 QLX 抓🐲筋 💌 玉女😘盘根 💌 臀滑🌈金三👅角 💌 👋🦶🦵🐻 出 💌 无限次 S牌原价638💰 🔥🔥🔥🔥 预约价568💰❤️❤️❤️❤️❤️ 时间75min 超A原价588💰💰💰🔥🔥 预约价528💰💰💰🔥🔥🔥 💗每天参加交流群抽奖或积分兑换 享劲爆价💰低至328元起/ 75min 🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰 全天25小时金牌🥇预约:(唯一预约号) 🚀电报: @Lysh888 📱电话徽信同号:18922310830 🥰交流群:https://t.me/Longyunshuihui 🥰推荐榜:https://t.me/Longyunshuihui2 🥰亲测榜:https://t.me/Lon

Signed 不叫吴彦祖 (小心骗子冒充我,群里面确认我的身份,不会主动私信任何人)

28 Sept 2026, 11:12 UTC147 viewsread 29 September 2026
Photo

珠江新城“秘境性疗愈”抓龙筋 私汤疗愈.湿身诱惑.专属情欲调教. SM调教.丝足cosplay . 轻柔舒服抓龙筋手法按摩.前列腺探索. 风格百变的感官刺激感受. 探索身体欲望的开关. 感受心底浪潮层层翻涌.奔赴灵魂潮汐.解锁颅内极致酥颤.收获全身心沉浸式感官治愈与专属快感、 QQ. 1435149882 微信. mi14784 电话.15914408689 联系 @cici6898 频道 https://t.me/mj3868

Signed 不叫吴彦祖 (小心骗子冒充我,群里面确认我的身份,不会主动私信任何人)

28 Sept 2026, 05:14 UTC204 viewsread 29 September 2026
Photo

老师花名 #cici #已验证 坐标 #佛山 #桂城 联系方式 @cici12134 频道 https://t.me/cici1012 价格 800p 1500pp

Signed 不叫吴彦祖 (小心骗子冒充我,群里面确认我的身份,不会主动私信任何人)

27 Sept 2026, 16:00 UTC233 viewsread 29 September 2026
Photo

老师花名 #怡宝 #已验证 坐标 #佛山 #南海 联系方式 @yb22331 频道 https://t.me/yb520cc 价格 600p 1100pp

Signed 小宝宝

27 Sept 2026, 13:36 UTC243 viewsread 28 September 2026
Photo

老师花名 #金沙 #已验证 坐标 #金沙洲 联系方式 @CoCobaobei666 频道 https://t.me/CoCodepengyouquan 价格 500p 900pp

Signed 陈冠希

27 Sept 2026, 07:25 UTC180 viewsread 28 September 2026
Photo

嫩妹情趣抚触性疗愈抓龙筋 丝足sm调教等多重玩法 带来极致放松与感官刺激 广州珠江新城隐秘空间 高端私享情趣按摩体验 沉浸式感官唤醒 涵盖暧昧互动角色体验 #男士调理 #抓龙筋 #男士SPA #天河区 电报联系 @fanmemg 频道 https://t.me/fanfanmengmeng 价格 抓龙筋499起

Signed 不叫吴彦祖 (小心骗子冒充我,群里面确认我的身份,不会主动私信任何人)

25 Sept 2026, 06:19 UTC379 views1 reactionsread 28 September 2026
Photo

老师花名 #梦瑶 #已验证 坐标 #海珠 联系方式 @qqaa887799 频道 https://t.me/yiyibaby111 价格 500

👍1

Signed 小宝宝

24 Sept 2026, 07:32 UTC653 views1 reactionsread 27 September 2026
Photo

🎰 若溪优惠劵活动 @mmfhy666 📮 抽奖条件: 🎫 加入-广州佛山修车大队LY之声 🎫 加入-广佛娱乐联盟总群 🎫 加入-诺溪朋友圈🏫 🎁 奖品内容: 15口令红包 × 1 100优惠劵 × 6 pp200优惠劵 × 6 夜400优惠劵 × 4 📅 开奖日期:(UTC+8) 2026年09月26日 15时31分21秒

👍1

Signed 抽奖机器人

24 Sept 2026, 07:23 UTC352 views1 reactionsread 27 September 2026
Photo

老师花名 #奶芙 #已验证 坐标 #番禺 联系方式 @zz998777itn 频道 https://t.me/yyyxhy520 价格 700p 1300pp

👍1

Signed 小宝宝

24 Sept 2026, 06:07 UTC324 views2 reactionsread 27 September 2026
Photo

老师花名 #甜甜 坐标 #天河 联系方式 @xiaoluoli6 频道 @xttluol1 价格 800p 1400pp

👍2

Signed 不叫吴彦祖 (小心骗子冒充我,群里面确认我的身份,不会主动私信任何人)

24 Sept 2026, 05:03 UTC327 views1 reactionsread 27 September 2026
Photo

全体注意全体注意⚠️⚠️⚠️,最近缅甸仔总是假冒我私信你们,你们的号是不会出现任何问题的,只要有任何一个人说你们的号有问题,直接拉黑

👍1

Signed 不叫吴彦祖 (小心骗子冒充我,群里面确认我的身份,不会主动私信任何人)

23 Sept 2026, 08:34 UTC≈1,440 views1 reactionsread 27 September 2026
Photo

老师花名 #雅雅 #已验证 坐标 #佛山 联系方式 @mmakk1314 频道 https://t.me/mmaitt 价格 600p 1000pp

👍1

Signed 不叫吴彦祖 (小心骗子冒充我,群里面确认我的身份,不会主动私信任何人)

Showing the 12 most recent of 72 posts we hold for @shenzhenxxhya. 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

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 1 registered channel — 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.

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

“广州佛山修车大队LY之声” (@shenzhenxxhya), 23,982 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/shenzhenxxhya.

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.