https://t.me/+6wo9CSr_fXY5NzM1

Channel
广西南宁黑天鹅榜
@nn55p
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
17,374subscribers
-336 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 | -1001584631044 |
|---|---|
| Type | Channel |
| Usernames | @nanning618 @nn55p |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 67 |
| Confirmed unchanged | 1 time, most recently 1 October 2026 |
| On Telegram | t.me/nn55p |
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 69% 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 |
|---|---|---|
| 1 Oct 2026, 06:17 | 17,374 | +13 |
| 24 Sept 2026, 20:01 | 17,361 | -47 |
| 18 Sept 2026, 17:16 | 17,408 | -4 |
| 18 Sept 2026, 06:18 | 17,412 | -9 |
| 16 Sept 2026, 12:21 | 17,421 | -2 |
| 16 Sept 2026, 01:42 | 17,423 | -7 |
| 14 Sept 2026, 16:21 | 17,430 | -2 |
| 14 Sept 2026, 09:58 | 17,432 | -20 |
| 13 Sept 2026, 03:16 | 17,452 | -5 |
| 12 Sept 2026, 15:58 | 17,457 | -18 |
| 11 Sept 2026, 06:57 | 17,475 | -4 |
| 10 Sept 2026, 14:38 | 17,479 | -11 |
| 8 Sept 2026, 12:39 | 17,490 | +2 |
| 7 Sept 2026, 12:17 | 17,488 | no change |
| 5 Sept 2026, 09:38 | 17,488 | +6 |
| 4 Sept 2026, 17:16 | 17,482 | -2 |
| 3 Sept 2026, 09:22 | 17,484 | -6 |
| 3 Sept 2026, 01:17 | 17,490 | -2 |
| 2 Sept 2026, 03:08 | 17,492 | +1 |
| 1 Sept 2026, 20:55 | 17,491 | first reading |
Engagement
72 posts held, back to 2 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 54 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 72 posts for this entry, the most recent from 2 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 23m 17s
- Average length
- 34s
Measured directly from 41 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
68 reactions across 31 posts, in 5 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 51 | 75.0% | |
| 👍 | 11 | 16.2% | |
| 😱 | 4 | 5.88% | |
| 👏 | 1 | 1.47% | |
| 💯 | 1 | 1.47% |
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 38 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 68 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 2 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
大概经过是这样的:男子在澳门美高酒店内和两名外籍女进行非法交易,等完事之后,身上的几万块不见了。男子发觉之后,急忙上街追出去找人,好不容易将对方拦下,可两名外籍女子一口咬定自己没有偷窃,并说双飞还无套,最后仅仅在包里找出一千港币。
❤3
要求真多100还要求换动作
❤1
Video, posted without a caption
记者暗访 金发妹妹 !
❤1
#曝光 #骗子 职业骗子抠脚大汉大家不要上当,半夜发假语音引诱关注频道,为什么你们总被动上当呢?事先能不能在群内问问群友,支付宝可以冻结和追回电诈钱,如果被骗直接向支付宝客服反馈被电诈要求冻结 🔔 任何主动私信即骗子,上门多数是骗子请慎重,不先给钱。警惕群内发QQ联系或说有学生妹、嫩妹、母狗等方式钓鱼骗定金。注意防冒充账号,要门槛即骗子,聊中要求对方即时发语音回复此法能过虑98%骗子,只约验证过的或公开榜上👉🏻 @nn812
餐前舞蹈 围着你搞
#曝光 #骗子 职业骗子抠脚大汉大家不要上当,半夜发假语音引诱关注频道,为什么你们总被动上当呢?事先能不能在群内问问群友,支付宝可以冻结和追回电诈钱,如果被骗直接向支付宝客服反馈被电诈要求冻结 🔔 任何主动私信即骗子,上门多数是骗子请慎重,不先给钱。警惕群内发QQ联系或说有学生妹、嫩妹、母狗等方式钓鱼骗定金。注意防冒充账号,要门槛即骗子,聊中要求对方即时发语音回复此法能过虑98%骗子,只约验证过的或公开榜上👉🏻 @nn812
https://t.me/+6wo9CSr_fXY5NzM1
买我的瓜忘记那个他
❤1
#曝光 被这个假中介坑了300,还被封号了
粉丝调侃孙宇晨被景甜割了
❤2
Showing the 12 most recent of 72 posts we hold for @nn55p. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@nn55p named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 16 August 2026 – 16 August 2026
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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“广西南宁黑天鹅榜” (@nn55p), 17,374 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/nn55p.
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.