❤️定位:#青秀 ❤️艺名:#淼淼 ❤️坐标:人照8分 ❤️私聊:@Wmiaomiao ❤️频道:https://t.me/miaomiaode12 ❤️课费:600p 1200pp ❤️备注:已押金认证 ❤️下方讨论区👇 ❤️交流群:https://t.me/+v3m1vLRq1yNjNmJl ✅认证:😀😀😀😀😀

Channel
南宁修机吧
@byxsm520
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
52,695subscribers
+3,803 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002153648377 |
|---|---|
| Type | Channel |
| Username | @byxsm520 |
| Description | 南宁修车哪家强?美女扳手耍得狂,车子有难不用慌,修机吧群担保来帮忙! 交流群: https://t.me/+v3m1vLRq1yNjNmJl 投诉 上榜: @jzdrbq_bot |
| Created | Between 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/byxsm520 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 17:57 | 52,695 | -2,099 |
| 4 Sept 2026, 03:41 | 54,794 | -1,025 |
| 2 Sept 2026, 14:23 | 55,819 | +15,003 |
| 1 Sept 2026, 15:25 | 40,816 | +3,380 |
| 31 Aug 2026, 16:06 | 37,436 | -638 |
| 30 Aug 2026, 17:57 | 38,074 | -1,023 |
| 29 Aug 2026, 21:14 | 39,097 | -416 |
| 29 Aug 2026, 00:28 | 39,513 | -991 |
| 27 Aug 2026, 23:05 | 40,504 | -176 |
| 27 Aug 2026, 00:04 | 40,680 | -337 |
| 26 Aug 2026, 03:29 | 41,017 | -421 |
| 25 Aug 2026, 03:23 | 41,438 | -712 |
| 23 Aug 2026, 21:04 | 42,150 | -445 |
| 22 Aug 2026, 02:07 | 42,595 | -782 |
| 20 Aug 2026, 16:15 | 43,377 | -319 |
| 19 Aug 2026, 16:37 | 43,696 | -560 |
| 18 Aug 2026, 19:18 | 44,256 | -215 |
| 17 Aug 2026, 20:43 | 44,471 | -526 |
| 16 Aug 2026, 22:05 | 44,997 | -730 |
| 15 Aug 2026, 16:25 | 45,727 | first reading |
Engagement
26 posts held, back to 4 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 68 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.603%
- avg views ÷ 52,695 subscribers
- Avg views / post
- 318
- 21 posts measured
- Reaction rate
- 0.265%
- reactions ÷ views · ER floor
- Posts in window
- 21
- of 26 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 10 of 21 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 September 2026 |
|---|---|
| Posts held | 26 (4 August 2026 – 6 September 2026) |
| Views total | 6,672 |
| Reactions total | 9 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Sept 2026, 20:25 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
- ≈1,800
- Videos
- ≈403
- Links
- ≈111
Lifetime counters from Telegram’s own channel header, read 6 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.
Reaction mix
11 reactions across 10 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 11 | 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 12 of the 26 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 11 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 26 most recent posts we hold, published 4 August 2026 to 6 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
❤️定位:#青秀 ❤️艺名:#糖糖 ❤️坐标:人照8分 ❤️私聊:@ling55520_bot ❤️频道:https://t.me/tt09872 ❤️课费:500p 900pp ❤️备注:已押金认证 ❤️下方讨论区👇 ❤️交流群:https://t.me/+v3m1vLRq1yNjNmJl ✅认证:😀😀😀😀😀
— 创作者中心 · 发视频赚USDT — 将超级引擎 @CJYQ 设置成管理员可收录您的频道/群组/让您的视频内容展现在小程序曝光获得流量 👇点击按钮体验视频号MiniApp吧👇
❤️定位:#青秀 ❤️艺名:#猫猫 ❤️坐标:人照8分 ❤️私聊:@diimkl ❤️频道:https://t.me/gjkfv57 ❤️课费:600p 1200pp ❤️备注:已押金认证 ❤️下方讨论区👇 ❤️交流群:https://t.me/+v3m1vLRq1yNjNmJl ✅认证:😀😀😀😀😀
❤1
#频道互推 #相似推荐 ------------------------------ 📢 深圳 95/96SPA 精品会所|同城推荐 📢 深圳会所95优质店 在线频道 📢 深圳本地 SPA 会所|95/96 专属服务 高端臻选 📢 广州万花 📢 95/96 服务 SPA 会所|深圳全城门店 📢 上海各区spa按摩红灯区 📢 深圳98楼凤修车探花选妃 📢 南京•约炮 📢 遵义上门 遵义外围 遵义修车 遵义约炮 📢 深圳迎春阁公开榜 ------------------------------ ☁️ 互推入口:@sososo
❤1
频道适合看内容,群组更适合继续交流。 SOSO 可以直接找热门群组,也能按关键词搜同类圈子。 先打开看看当前推荐。
❤️定位:#青秀 ❤️艺名:#李若雪 ❤️坐标:人照8分 ❤️私聊:@liruoxue ❤️频道:https://t.me/liruoxue168 ❤️课费:600p 1200pp ❤️备注:已押金认证 ❤️下方讨论区👇 ❤️交流群:https://t.me/+v3m1vLRq1yNjNmJl ✅认证:😀😀😀😀😀
❤1
❤️定位:#青秀 ❤️艺名:#酥酥 ❤️坐标:人照8分 ❤️私聊:@Su998801 ❤️频道:https://t.me/susu2431 ❤️课费:700p 1400pp ❤️备注:已押金认证 ❤️下方讨论区👇 ❤️交流群:https://t.me/+v3m1vLRq1yNjNmJl ✅认证:😀😀😀😀😀
— 创作者中心 · 发视频赚USDT — 将超级引擎 @CJYQ 设置成管理员可收录您的频道/群组/让您的视频内容展现在小程序曝光获得流量 👇点击按钮体验视频号MiniApp吧👇
🤖极速极搜JSJS开启全能引擎新时代 📊全国同城约会可精准挑选地区 📈真实用户月活量100万+ ⚡️门槛低、反应快、流量大 📍极速的响应,极致的搜索 TG全新引擎功能全面上线 极速极搜唯一四位ID:JSJS ✅ 加入官方频道 | 🤖 机器人助手 | 💬 客服咨询 新用户点此文案下方链接进入极速极搜,你会获得0.3$拉新奖励 将极速极搜引擎拉入群聊并设置管理权限收益可日入百U
❤️定位:#青秀 ❤️艺名:#嫣然 ❤️坐标:人照8分 ❤️私聊:@yueyue11682 ❤️频道:https://t.me/yueyuepindao6 ❤️课费:600p 1200pp ❤️备注:已押金认证 ❤️下方讨论区👇 ❤️交流群:https://t.me/+v3m1vLRq1yNjNmJl ✅认证:😀😀😀😀😀
❤1
❤️定位:#青秀 ❤️艺名:#小丫丫 ❤️坐标:人照8分 ❤️私聊:@xml618 ❤️频道:https://t.me/xml818 ❤️课费:600p 1200pp ❤️备注:已押金认证 ❤️下方讨论区👇 ❤️交流群:https://t.me/+v3m1vLRq1yNjNmJl ✅认证:😀😀😀😀😀
Showing the 12 most recent of 26 posts we hold for @byxsm520. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
@cjyq · 895,0115 postsSOSO搜搜
@sooo · 612,6773 posts酥酥个人💗朋友圈
@susu2431 · 4142 posts猫猫🐱本人兼职 c➕
@gjkfv57 · 5751 post南宁精灵的新花园
@jlxhy999 · 4821 post极速极搜官方公告
@jsjs7 · 24,1001 post南宁 个人兼职李若雪
@liruoxue168 · 2,6961 post七七❤️朋友圈
@qi2300 · 1911 postSOSO搜搜
@sososo · 553,9071 post小思涵(个人自聊) つ😘つ
@ydwh31 · 1,3201 post竹竹🍑朋友圈
@zhuzhuzhubaby · 3,1761 post
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“南宁修机吧” (@byxsm520), 52,695 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/byxsm520.
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.