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,459subscribers

-3,890 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
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 live29 October 2026
Measurements held50
Confirmed unchanged1 time, most recently 29 October 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 the other topics.

Growth

23,45927,35025,404.57 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 subscribers3 October 2026 — 23,827 subscribers8 October 2026 — 23,786 subscribers12 October 2026 — 23,807 subscribers14 October 2026 — 23,751 subscribers15 October 2026 — 23,584 subscribers16 October 2026 — 23,574 subscribers17 October 2026 — 23,571 subscribers18 October 2026 — 23,568 subscribers20 October 2026 — 23,562 subscribers22 October 2026 — 23,547 subscribers23 October 2026 — 23,496 subscribers24 October 2026 — 23,478 subscribers25 October 2026 — 23,482 subscribers26 October 2026 — 23,483 subscribers27 October 2026 — 23,482 subscribers28 October 2026 — 23,474 subscribers29 October 2026 — 23,459 subscribers7 August 202629 October 2026
50 measurements spanning 83 days, net -3,890. 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 22,875–27,934 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 50
Measured (UTC)SubscribersChange
29 Oct 2026, 05:3923,459-15
28 Oct 2026, 02:0023,474-8
27 Oct 2026, 04:0723,482-1
26 Oct 2026, 01:2623,483+1
25 Oct 2026, 00:2723,482+4
24 Oct 2026, 01:5823,478-18
23 Oct 2026, 04:0523,496-51
22 Oct 2026, 01:0123,547-15
20 Oct 2026, 18:0923,562-6
18 Oct 2026, 13:5023,568-3
17 Oct 2026, 11:5623,571-3
16 Oct 2026, 10:0123,574-10
15 Oct 2026, 12:3123,584-167
14 Oct 2026, 11:5923,751-56
12 Oct 2026, 21:4923,807+21
8 Oct 2026, 09:1923,786-41
3 Oct 2026, 23:4123,827-155
25 Sept 2026, 07:1623,982-1,752
17 Sept 2026, 05:0125,734+252
15 Sept 2026, 06:3825,482first reading

Engagement

120 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 104 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.85%
avg views ÷ 23,459 subscribers
Avg views / post
904
47 posts measured
Reaction rate
0.089%
reactions ÷ views · ER floor
Posts in window
47
of 120 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 47 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 October 2026
Posts held120 (5 August 2026 – 28 October 2026)
Views total42,481
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Oct 2026, 08:36 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
5m 57s
Average length
10s

Measured directly from 37 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

22 reactions across 18 posts, in 2 distinct kinds. The most used accounts for 95.5% of them.

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

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

Measured over the 120 most recent posts we hold, published 5 August 2026 to 28 October 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 Oct 2026, 03:43 UTC≈2,150 viewsread 28 October 2026
Photo

老师花名 #林汐 #已验证 坐标 #越秀 联系方式 @linlinxi666 频道 https://t.me/linxi_528 价格 800p 1500pp

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

27 Oct 2026, 07:12 UTC≈1,470 viewsread 28 October 2026
Photo

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

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

27 Oct 2026, 06:12 UTC≈1,470 viewsread 28 October 2026
Photo

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

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

24 Oct 2026, 10:46 UTC≈1,050 viewsread 24 October 2026
Photo

94抓龙筋 坐标 #三元里 #罗冲围 联系方式 @ww01168168 微信:tlg520spa 频道 https://t.me/GzYx520 价格 538起

Signed 陈冠希

22 Oct 2026, 16:20 UTC≈1,350 views1 reactionsread 24 October 2026
Photo

老师花名 #艳子 #已验证 坐标 #海珠 联系方式 @yan73683 频道 https://t.me/yan8379 价格 400p

👍1

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

22 Oct 2026, 05:52 UTC≈1,380 views1 reactionsread 24 October 2026
Photo

老师花名 #瑶瑶 #已验证 坐标 #佛山 #桂城 联系方式 @Make_tea6600 频道 http://t.me/Mwyhk0001 价格 400p

👍1

Signed 陈冠希

18 Oct 2026, 10:46 UTC≈1,690 viewsread 23 October 2026
Photo

📍#天河 #燕塘 #东莞庄 #粤垦路 #天平架 #岗顶 #颜值嫩妹 #优质会所 🥰🥰🥰 Ym·Mens94会所 课程内容🔖综合简介 (优质9️⃣4️⃣场) 老师帮洗浴🛁洗澡~🛁🛁泡泡浴 热舞💃互动 ~ 制服👙高跟👠丝袜 半🍎真🐻漫游 ~ 🐍尖采蜜三角部位 🐍尖👃息💋吸AB面 ~ 小猫钓鱼 (🈚️口臭ls🉑嘴亲)👅🥚🥚、 (全🍎真69🤸‍♀️互👅) 🐍吻等君品鉴 波涛汹涌,M🦵S🦶,六九式诱惑 猴子偷桃🍑,肾宝键抓🐲筋服认真 可选👋🦶🦵🐻 出 ~ 💦不限次😍 🥰🥰 (私聊看详细课程介绍) 🥰🥰 💥提前预约仅收4️⃣4️⃣8️⃣元/ 70 分钟(🉑✌️💦) 主打00-08年高颜值,没有肥老胖丑💃 群活动🎡海量白嫖劵, 半价劵, 红包🧧等抽奖福利🌟 进群积分抽奖🎟🉑免费白嫖,更多148~348低价福利💥@xyspa1 全天金牌🥇预约:扁鹊💋 🚀电报: @drj1…

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

18 Oct 2026, 05:47 UTC≈1,400 viewsread 21 October 2026
Photo

老师花名 #狂野 #已验证 坐标 #天河 联系方式 @fcmhj88y 频道 @hjm52088y 价格 1200p 2000pp

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

18 Oct 2026, 05:46 UTC≈1,380 viewsread 21 October 2026
Photo

老师花名 #蜜桃 坐标 #天河 联系方式 @mitao822 QQ 3948556344 频道 https://t.me/mitao220 价格 800p 1400pp

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

15 Oct 2026, 09:09 UTC≈3,420 views1 reactionsread 15 October 2026
Photo

😁😆🥹 🥰 🥰 🫠🫠 🫠🫠🫠🫠 🫠🫠🫠🫠 广州 #天河#网红场#颜值天花板#车陂#RX玖二#玖三 #玖四花式#🐻推# 丝足 #广州会所 📖课程✨花式玖二#玖三#玖四#⛽️👚🌸式半果👙 花式六九👅🥚,👋 推&🦵推~🐻推~漫游~💃艳舞诱惑~ 枕边游戏, 多种制服👗黑丝诱惑等等😚无限次,期待您亲临体验💯大型停车场🅿️免费停车,免费WF📶自助餐棋牌24小时🈺业 🔥🔥🔥主打 0️⃣0️⃣后0️⃣5️⃣后👩高品质.高颜值嫩妹 24小时🈺业,免费停车🚗、📶、自助餐。 预约价: 女王牌-6️⃣3️⃣8️⃣💰-7️⃣0️⃣🕰 至尊牌-5️⃣9️⃣8️⃣💰-7️⃣0️⃣🕰 瑞星牌-5️⃣6️⃣8️⃣💰-8️⃣0️⃣🕰 明星牌-5️⃣3️⃣8️⃣💰-8️⃣0️⃣🕰 更多详情请咨询或拨打…… 欢乐热线☎️:微信同步 瑶瑶:19924791936 小爱:19303062991 一一:18802290938 广州瑞星…

👍1

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

14 Oct 2026, 10:04 UTC≈1,540 viewsread 15 October 2026
Photo

老师花名 #甜心 #已验证 坐标 #天河 联系方式 @tianxin56889 频道 https://t.me/xtx5698 价格 500

Signed 小宝宝

14 Oct 2026, 06:30 UTC≈1,590 viewsread 15 October 2026
Photo

老师花名 #菲菲 #已验证 坐标 #佛山 联系方式 @fsffzlj 频道 https://t.me/foshanfeifei 抓龙筋358/60min起

Signed 陈冠希

Showing the 12 most recent of 120 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“广州佛山修车大队LY之声” (@shenzhenxxhya), 23,459 subscribers as measured 29 October 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.