Telegram RegisterThe public register of Telegram
Telegram profile photo for 南山 金泫雅的朋友圈

Channel

南山 金泫雅的朋友圈

@nanshanjxy0706

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1,143subscribers

-51 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002209038018
TypeChannel
Username@nanshanjxy0706
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/nanshanjxy0706

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 18 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 why it has no browse page of its own yet.

Growth

1,1431,1941,168.57 August 2026 — 1,194 subscribers7 August 2026 — 1,193 subscribers10 August 2026 — 1,190 subscribers12 August 2026 — 1,186 subscribers16 August 2026 — 1,178 subscribers19 August 2026 — 1,174 subscribers22 August 2026 — 1,173 subscribers25 August 2026 — 1,166 subscribers28 August 2026 — 1,164 subscribers31 August 2026 — 1,158 subscribers3 September 2026 — 1,156 subscribers9 September 2026 — 1,152 subscribers12 September 2026 — 1,147 subscribers16 September 2026 — 1,143 subscribers7 August 202616 September 2026
14 measurements spanning 40 days, net -51. 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 1,135–1,202 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 04:181,143-4
12 Sept 2026, 19:421,147-5
9 Sept 2026, 03:591,152-4
3 Sept 2026, 18:411,156-2
31 Aug 2026, 14:251,158-6
28 Aug 2026, 04:431,164-2
25 Aug 2026, 04:571,166-7
22 Aug 2026, 00:381,173-1
19 Aug 2026, 01:071,174-4
16 Aug 2026, 09:041,178-8
12 Aug 2026, 18:031,186-4
10 Aug 2026, 02:021,190-3
7 Aug 2026, 12:351,193-1
7 Aug 2026, 11:011,194first reading

Engagement

15 posts held, back to 17 December 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 15 posts for this entry, the most recent from 13 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

12 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
975.0%
👍216.7%
🥰18.33%

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

Measured over the 15 most recent posts we hold, published 17 December 2024 to 13 February 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

13 Feb 2026, 08:08 UTC866 viewsread 7 August 2026

闺蜜在深圳,关注一下吧! 私聊 @nszrn999 双向 @nszrn999Bot 频道 https://t.me/+65kofX76iHNlMGZh

8 Jan 2025, 06:57 UTC≈7,640 views2 reactionsread 7 August 2026

各位哥哥宝子们😂我先回家过年了哈,年后再见💋💋💋 提前祝您们身体健康,万事如意,大顺大财大吉祥😁😁😁

2

5 Jan 2025, 09:24 UTC≈7,670 views3 reactionsread 7 August 2026
Photo

你们都忙着年终总结,我就一个人静静地总结自己⌨️⌨️⌨️

2🥰1

2 Jan 2025, 03:48 UTC≈5,070 viewsread 7 August 2026
Photo

明天(3号)回深,上午10.30左右开课👩🏻‍🎓

1 Jan 2025, 11:14 UTC≈4,090 views0 reactionsread 7 August 2026
Photo

🍻🎊 新的一年到啦🚀🚀 祝你元旦快乐,天天开心,万事如意哦!💖🎁✨ (ღ✪v✪)ღ新年吉祥~ 🎉🥳💐

22 Dec 2024, 06:37 UTC≈4,210 views3 reactionsread 7 August 2026
Photo

香港一日游,开心的疲惫,回来啦,继续搬砖牛马😆😆😆

2👍1

19 Dec 2024, 11:19 UTC≈4,710 views2 reactionsread 7 August 2026

#出击模板 【出击报告】 验证留名:yuelun 老师昵称:#南山 金泫雅 电报号: @nanshanjxy 出击时间:2024-12月13 地市坐标:#深圳 #南山 上课花费:1300P 出击体验: 我已经去过五六次了,每一次都很沉浸,沉浸的不是肉体本身,而是和她在一起的情感欢愉。 就跟女朋友一样,她知道你喜欢什么,会跟你分享她的生活和故事,会和你嬉笑怒骂,会和你耳鬓厮磨,会跟你纠缠拉扯 做爱时也是这样,她的奔放,狂野,可爱,性感,还有情到深处的咬动,都让人情不自禁的怀念 所以说不是肉体本身,是那种情绪的拿捏,是最让人上头的 她每次都让我写,我迟迟不写,就是因为不想让太多人知道她的魅力 没有群主只有玩家,纯分享纯交流群 ( https://t.me/SZHKFriends ) 报告提交群秘书: @SZHKFriends2_bot 或 @SZHKFriendszy_bot 深港老友会分享报告频道: @SZHKFrien

1👍1

19 Dec 2024, 04:43 UTC≈3,350 viewsread 7 August 2026

阳光明媚的一天开始了,祝你有个美好心情!☀

Showing the 12 most recent of 15 posts we hold for @nanshanjxy0706. 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

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 September 2026 — this entry's latest reading, not the date you are reading this.

“南山 金泫雅的朋友圈” (@nanshanjxy0706), 1,143 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/nanshanjxy0706.

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.