Telegram RegisterThe public register of Telegram
Telegram profile photo for 南京外围中圈资源【Supreme】

Channel

南京外围中圈资源【Supreme】

@Nansadd

2 usernames

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

16,607subscribers

+5,239 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002109571630
TypeChannel
Usernames@inbig @Nansadd
Description南京 Supreme 超人气约会是南京领先的高端约会服务品牌,我们建立严格的品质把控,进行精准匹配,提升见面质量与后续转化率。陪同执行与复盘跟进,全链路把控体验与安全。打造私密格调的约会场景。选择南京 Supreme,意味着选择更专业、更可靠的相遇方式。 Sup会员出击交流群:https://t.me/golabel Sup中端选妃频道:https://t.me/inbig Supreme莱恩 @d1688r 双向限制🚫无法私信 @Supremeii_BOT
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live3 November 2026
Measurements held112
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/Nansadd

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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

11,36816,60713,987.58 August 20263 November 2026
112 measurements spanning 88 days, net +5,239. 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 10,582–17,393 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 112
Measured (UTC)SubscribersChange
3 Nov 2026, 21:4816,607+9
3 Nov 2026, 12:1116,598+128
2 Nov 2026, 18:5516,470+13
2 Nov 2026, 13:3616,457+125
1 Nov 2026, 16:1716,332no change
1 Nov 2026, 13:1916,332+58
31 Oct 2026, 17:0716,274-3
31 Oct 2026, 12:2616,277+60
30 Oct 2026, 13:5516,217+38
30 Oct 2026, 12:1816,179+42
29 Oct 2026, 15:2116,137+46
29 Oct 2026, 10:2716,091+67
28 Oct 2026, 15:1816,024+29
28 Oct 2026, 10:0015,995+82
27 Oct 2026, 16:5515,913+56
27 Oct 2026, 10:0915,857+37
26 Oct 2026, 19:5115,820+11
26 Oct 2026, 12:1815,809+63
25 Oct 2026, 21:1915,746+32
25 Oct 2026, 13:3115,714first reading

Engagement

44 posts held, back to 29 July 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 52 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.91%
avg views ÷ 16,607 subscribers
Avg views / post
981
11 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
11
of 44 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 November 2026
Posts held44 (29 July 2026 – 3 November 2026)
Views total10,789
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 04:08 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
≈345
Videos
≈1,110
Links
≈576

Lifetime counters from Telegram’s own channel header, read 4 November 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.

Video runtime
7m 15s
Average length
10s

Measured directly from 44 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.

Recent posts

3 Nov 2026, 08:55 UTC831 viewsread 4 November 2026
Photo

南京:#未验证 花名:#甜甜 位置:#秦淮 #文思新村 类型:#嫩妹 #08 服务:#舌吻 #外出 #包夜 #制服 #陪浴 价格:1300/70分钟/2次 💱交流群组 🎉反馈返现100 💬点此预约 ⚠️️私信限制

Signed Supreme『南京莱恩』

3 Nov 2026, 08:24 UTC819 viewsread 4 November 2026
Photo

南京:#已验证 花名:#迟遇 位置:#江宁 #正荣•润峰 类型:#御姐 服务:#陪浴 #指划 #胸推 #制服 #外出 价格:1300/70分钟/2次 💱交流群组 🎉反馈返现100 💬点此预约 ⚠️️️私信限制

Signed Supreme『南京莱恩』

3 Nov 2026, 04:13 UTC≈1,020 viewsread 4 November 2026
Video

南京:#未验证 花名:#樱桃 位置:#江宁 #中海龙湾 类型:#嫩妹 服务:#舌吻 #六九 #胸推 #制服 #足交 价格:1300/70分钟/2次 💱交流群组 🎉反馈返现100 💬点此预约 ⚠️️私信限制

Signed Supreme『南京莱恩』

3 Nov 2026, 02:38 UTC≈1,900 viewsread 4 November 2026
Video

预约流程🔸反馈模板🔸VPN推荐 出击报告🔸积分优惠🔸中圈资源 大圈资源🔸私信限制🔸官方客服 👉中端1200:【1300反馈返100】 👉高端2200:【2400反馈返200】 🔤🔤🔤🔤🔤🔤🔤 11/04红牌推荐⤵️ 小七 雨蒙 佳琪 小雨 豆苗 江宁区推荐⤵️ 艾伦 甜甜 余悦 娇娇 欣妍 图图 紫怡 嘉悦 洁洁 橙子 紫晗 芮一 熙雯 果果 兔子 草莓 依依 一宝 乖儿 建邺区推荐⤵️ 瑶瑶 姗姗 开心 怡宝 北北 悠悠 不点 夏洛 美熙 鼓楼区推荐⤵️ 宝宝 六月 小鹿 媚娘 秦淮/栖霞/浦口区推荐⤵️ 戚薇 韩佳 菲菲 阳阳 莹莹 🔸推荐榜单仅是莱恩筛选出来的优质老师名单,并非全部开工老师 🔸蓝色字体均为老师名字,点击蓝色字体可查看老师详细资料 🔸极少部分老师可单次,如需单次可联系客服 🔸推荐榜…

Signed Channel Help

2 Nov 2026, 14:02 UTC≈1,200 viewsread 4 November 2026
Video

南京:#已验证 花名:#晴晴 位置:#江宁 #景峰科技大厦 类型:#嫩妹 服务:#舌吻 #六九 #无套 #陪浴 #包夜 价格:1300/70分钟/2次 💱交流群组 🎉反馈返现100 💬点此预约 ⚠️️私信限制

Signed Supreme『南京莱恩』

2 Nov 2026, 14:00 UTC≈1,120 viewsread 4 November 2026
Photo

南京:#已验证 花名:#阳阳 位置:#秦淮 #下浮桥面馆 类型:#少妇 服务:#舌吻 #六九 #艳舞 #陪浴 价格:1500/70分钟/2次 💱交流群组 🎉反馈返现100 💬点此预约 ⚠️️私信限制

Signed Supreme『南京莱恩』

2 Nov 2026, 07:50 UTC≈1,100 viewsread 4 November 2026
Video

南京:#已验证 花名:#梦瑶 位置:#江宁 #同曦大厦 类型:#嫩妹 服务:#舌吻 #包夜 #制服 #口爆 价格:1300/70分钟/2次 💱交流群组 🎉反馈返现100 💬点此预约 ⚠️️私信限制

Signed Supreme『南京莱恩』

2 Nov 2026, 07:48 UTC717 viewsread 3 November 2026
Photo

南京:#未验证 花名:#雯儿 位置:#鼓楼 #阳光金峰 类型:#嫩妹 服务:#漫游 #六九 #陪浴 #制服 #裸吹 价格:1300/70分钟/2次 💱交流群组 🎉反馈返现100 💬点此预约 ⚠️️私信限制

Signed Supreme『南京莱恩』

2 Nov 2026, 07:46 UTC682 viewsread 3 November 2026
Video

南京:#已验证 花名:#媚娘 位置:#鼓楼 #世贸外滩 类型:#少妇 服务:#漫游 #六九 #口爆 #制服 价格:1300/70分钟/2次 💱交流群组 🎉反馈返现100 💬点此预约 ⚠️️私信限制

Signed Supreme『南京莱恩』

2 Nov 2026, 07:43 UTC666 viewsread 3 November 2026
Photo

南京:#已验证 花名:#美依 位置:#江宁 #亲水湾花园 类型:#少妇 服务:#舌吻 #六九 #无套 #胸推 #深喉 价格:1300/70分钟/2次 💱交流群组 🎉反馈返现100 💬点此预约 ⚠️️私信限制

Signed Supreme『南京莱恩』

2 Nov 2026, 06:34 UTC734 viewsread 3 November 2026
Video

南京:#已验证 花名:#艾伦 位置:#江宁 类型:#女友 #清纯 服务: #舌吻 #六九 #制服 #高跟 #指划 #陪浴 #五套 价格:1300/70分钟/2次 💌【报告01】 💌【报告02】 💌【报告03】 💌【报告04】 💌【报告05】 💌【报告06】 💌【报告07】 💌【报告08】 💌【报告09】 💌【报告10】 💌【报告11】 💌【报告12】 💌【报告13】 💱交流群组 🎉反馈返现100 💬点此预约 ⚠️️️私信限制

Signed Supreme『南京莱恩』

2 Sept 2026, 12:17 UTC509 viewsread 2 September 2026
Video

南京:#已验证 花名:#雨蒙 位置:#江宁 #上善居 类型:#嫩妹 服务:#助浴 #舌吻 #指划 #胸推 #调情 #无套 价格:1300/70分钟/2次 💱交流群组 🎉反馈返现100 💬点此预约 ⚠️️️️️️️️️️️️️️私信限制

Signed Supreme『南京莱恩』

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

Posts edited after publishing

@Nansadd edited 7 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
8 August 2026
Most recent edit
4 November 2026

Posts recorded as deleted after publishing

We recorded 6 posts on @Nansadd as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
11 August 2026
Most recent seen missing
1 September 2026
Median time before seen missing
6 days
Seen missing in the last 30 days
0

Mentions

Named by 3 registered channels — 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.

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

“南京外围中圈资源【Supreme】” (@Nansadd), 16,607 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/Nansadd.

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.