https://t.me/SZchunv02

Channel
频道共享
@nanren6
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
6,369subscribers
+164 since we began measuring on 28 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002380383882 |
|---|---|
| Type | Channel |
| Username | @nanren6 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 September 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/nanren6 |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 13:09 | 6,369 | +19 |
| 11 Nov 2026, 01:07 | 6,350 | +26 |
| 7 Nov 2026, 00:30 | 6,324 | +13 |
| 4 Nov 2026, 06:16 | 6,311 | -64 |
| 1 Nov 2026, 12:50 | 6,375 | +8 |
| 29 Oct 2026, 16:48 | 6,367 | +22 |
| 26 Oct 2026, 09:56 | 6,345 | +27 |
| 23 Oct 2026, 00:16 | 6,318 | +19 |
| 20 Oct 2026, 04:27 | 6,299 | +18 |
| 17 Oct 2026, 13:30 | 6,281 | +7 |
| 14 Oct 2026, 18:50 | 6,274 | +4 |
| 11 Oct 2026, 15:42 | 6,270 | +27 |
| 4 Oct 2026, 21:54 | 6,243 | +38 |
| 28 Sept 2026, 07:22 | 6,205 | no change |
| 28 Sept 2026, 06:47 | 6,205 | first reading |
Engagement
21 posts held, back to 20 June 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 6 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.03%
- avg views ÷ 6,369 subscribers
- Avg views / post
- 129
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 21 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.
| Window | Rolling 30 days · latest post in window 3 November 2026 |
|---|---|
| Posts held | 21 (20 June 2025 – 3 November 2026) |
| Views total | 129 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 13:50 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.
Reaction mix
23 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 87.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 20 | 87.0% | |
| 👍 | 1 | 4.35% | |
| 🔥 | 1 | 4.35% | |
| 😁 | 1 | 4.35% |
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 11 of the 21 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 23 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 20 June 2025 to 3 November 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
Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
https://t.me/+Xs4Dfz3yjVg3OTk1
❤2
https://t.me/SZchunv01
https://t.me/shanghaiZY01
❤2
https://t.me/beijingZY01
❤1
https://t.me/tgcn66
https://t.me/WWsz520
https://t.me/C00852
https://t.me/xianggang186
https://t.me/joinchat/WHr9RQmlL6wM49uH
https://t.me/HKSC168
❤1
https://t.me/qingdaoZY01
Showing the 12 most recent of 21 posts we hold for @nanren6. 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
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.
Names
Channels on the register whose handles appear in this channel's posts.
@beijingZY01 · 16,9761 postC家👉睇图频道【香港🇭🇰沙田-天水围】(日日更新)
@C00852 · 12,0561 post重庆成都修车交流【川蜀一家亲】
@chongqingZY01 · 4,7711 post杭州修车【认证榜单】
@hangzhouZZB · 4,1991 post香港18区🩸帅哥美女🩸聊天群🈲🔞
@HKliaotian02 · 17,0261 post🔥SC🔥睼图频道❤️(香港🇭🇰尖沙咀每日更新🥇)
@HKSC168 · 12,8111 post惠州修车资源【交流群】🍌🍌🍌
@huizhouZY01 · 19,9631 post深圳商K/摸摸唱/商务KTV/真空游戏场
@KTV1588888 · 6,5871 post青岛济南修车认证榜
@qingdaoZY01 · 7,4701 post上海【狼友学院】【交流群】🚀🚀
@shanghaiZY01 · 29,5161 post上海修车【认证榜单】
@shanghaiZZB · 5,5011 post深圳处女(🉑空降)
@SZchunv01 · 9,2511 posttelegram中文社区
@tgcn66 · 6,7121 post深圳广州修车精选【已认证】💃💃💃
@WWsz520 · 36,6751 post深圳广州香港澳门【大湾区💘🔞】
@xianggang186 · 53,0851 postYY澳门🇲🇴美女频道❤️【天天更新】
@YY00853 · 5,8161 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“频道共享” (@nanren6), 6,369 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/nanren6.
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.