‼️‼️给大家推荐24H南宁会所‼️‼️ 🆕 店家自营6️⃣家会所-没有中介赚差价 💎 「南宁-最牛逼的全裸海选水疗会所」 💃 频道内的女孩照片都是真实的 💎 详细服务流程看频道信息【@LaoWangZhongZhuan888】 ⚡️ 详细请点击南宁老王学院查看- @NanNingXueYuan888 ⚡️ 24H海选全裸会所预约- @NanNing94HuiSuoBot

Channel
广西南宁道侣榜
@NnXx_99
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
14,734subscribers
+34 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003042363833 |
|---|---|
| Type | Channel |
| Username | @NnXx_99 |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/NnXx_99 |
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 85% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 10:39 | 14,734 | -8 |
| 8 Sept 2026, 19:36 | 14,742 | +24 |
| 5 Sept 2026, 10:17 | 14,718 | +1 |
| 3 Sept 2026, 13:56 | 14,717 | +18 |
| 2 Sept 2026, 09:27 | 14,699 | +3 |
| 1 Sept 2026, 09:15 | 14,696 | +17 |
| 31 Aug 2026, 05:54 | 14,679 | +15 |
| 30 Aug 2026, 06:08 | 14,664 | -8 |
| 29 Aug 2026, 08:27 | 14,672 | -8 |
| 28 Aug 2026, 08:33 | 14,680 | +1 |
| 27 Aug 2026, 08:22 | 14,679 | -1 |
| 26 Aug 2026, 05:37 | 14,680 | -5 |
| 25 Aug 2026, 05:48 | 14,685 | +2 |
| 24 Aug 2026, 04:06 | 14,683 | +35 |
| 22 Aug 2026, 09:14 | 14,648 | +6 |
| 20 Aug 2026, 21:58 | 14,642 | +27 |
| 19 Aug 2026, 20:29 | 14,615 | +4 |
| 18 Aug 2026, 20:26 | 14,611 | -34 |
| 17 Aug 2026, 17:06 | 14,645 | -2 |
| 16 Aug 2026, 08:34 | 14,647 | first reading |
Engagement
26 posts held, back to 8 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 39 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 9.67%
- avg views ÷ 14,734 subscribers
- Avg views / post
- 1,430
- 19 posts measured
- Reaction rate
- 0.087%
- reactions ÷ views · ER floor
- Posts in window
- 19
- 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 12 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 26 (8 August 2026 – 2 September 2026) |
| Views total | 27,081 |
| Reactions total | 17 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 18:23 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
- 3m 10s
- Average length
- 15s
Measured directly from 13 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 12 posts, in 3 distinct kinds. The most used accounts for 81.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 18 | 81.8% | |
| 👎 | 3 | 13.6% | |
| 🔥 | 1 | 4.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 16 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 22 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 8 August 2026 to 2 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
【花名】:#御姐范 【地区】:#南宁 #青秀区 【价格】:600p 1200PP 【联系】: @yujiefant 【服务】:🐍吻 🈚️T口 陪浴 丝袜, 【报告】: 🥰南宁散修俱乐部
【花名】:#小七 【地区】:#南宁 #青秀区 【价格】:600p 1200PP 【联系】: @dyy2530 【服务】:🐍吻 69 按摩 情趣丝袜.. 【报告】:作业1 🥰南宁散修俱乐部
【花名】:#娜娜 【地区】:#南宁 #青秀区 【价格】:600p 1200PP 【联系】:@nn325468 【服务】:🐍吻 🈚️T口 陪浴 丝袜情趣.. 【报告】:作业1 🥰南宁散修俱乐部
【花名】:#兔兔 【地区】:#南宁 #西乡塘 【价格】:600p 1200pp 【联系】:@tutu00988 【服务】:https://t.me/tutu00998 【报告】: 🥰南宁散修俱乐部
❤1
【花名】:#云伊 【地区】:#南宁 #青秀区 【价格】:600p 1200PP 【联系】:@qwea1314789 【服务】:🐍吻 69 水中萧 制服情趣.. 【报告】:作业1 作业2 作业3 🥰南宁散修俱乐部
【花名】:#柚子 【地区】:#南宁 #青秀区 【价格】:600p 1200PP 【联系】:@Lidreu 【服务】:kiss 陪浴 🈚️套口 情趣丝袜.. 【报告】: 🥰南宁散修俱乐部
【花名】:#李师师 【地区】:#南宁 #青秀区 【价格】:600p 1200PP 【联系】: @lishishie 【服务】:蛇纹,69,水中萧,据说高颜值御姐 【报告】:作业1 作业2 🥰南宁散修俱乐部
南宁各区平价快餐,价格写到地址上,4/5张一次这样,低端外卖500加100车费,需要先给车费。中端1300两次 高端1900-2500左右两次 ❤️看图确定来再私聊我要定位, 全部免费提供公寓房间,到后拍照确认,见到妹子合适后付费给小妹,不合适就撤或换,不收任何预约订金 💗安排联系 @chaxiaoer2 双向联系 @nanning_001_bot 选妃频道:https://t.me/nanning001_channel
【花名】:#润多多 【地区】:#南宁 #青秀区 【价格】:700p 1300PP 【联系】: @runduiduo 【服务】:69 深喉 水中萧 据说是个空姐有待验证 【报告】:作业1 🥰南宁散修俱乐部
❤3🔥1
南宁高端外围,诚信靠谱空姐, 主打特色服务,无套,舔足 舔阴,足交 ,女奴 ,颜射,裸舞, 舌吻,抠B,重SM,肛交,吞精,制服 ,道具,白虎,处女等等(无套,孕妇,奶妈,三通 SM 拍视频,喷水)诚信安排不走弯路,频道中只上传了少量老师,每天100多位在线。(柳州,桂林等) 营业时间:中午13点到凌晨5点, 飞机私信: @snspa0771 双向飞机联系: @snspabot 高端选妃频道: https://t.me/nnsap 群组:https://t.me/snspa 类型标签: #嫩妹 #御姐 #少女 #工作室 #可上门 #可舌吻 #可69 (妹子有地方,无需预约定金.也可以安排上门)
❤2
【花名】:#小龙女 【地区】:#南宁 #青秀区 【价格】:600p 1100PP 【联系】:@tz20050505 【服务】:🐍吻 69 深喉 丝袜.. 【报告】:作业1 作业2 作业3 作业4 🥰南宁散修俱乐部
❤1
Showing the 12 most recent of 26 posts we hold for @NnXx_99. 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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“广西南宁道侣榜” (@NnXx_99), 14,734 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/NnXx_99.
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.