Telegram RegisterThe public register of Telegram
Telegram profile photo for 南栀的后花园

Channel

南栀的后花园

@nanzhi1314

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,209subscribers

+370 since we began measuring on 29 August 2026

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

Register entry

Telegram ID-1003761895939
TypeChannel
Username@nanzhi1314
CreatedBetween 1 February 2026 and 5 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live11 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/nanzhi1314

Growth

8391,2411,04029 August 2026 — 839 subscribers29 August 2026 — 1,019 subscribers2 September 2026 — 1,241 subscribers6 September 2026 — 1,222 subscribers11 September 2026 — 1,209 subscribers1,20929 August 202611 September 2026
5 measurements spanning 13 days, net +370. 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 779–1,301 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 06:211,209-13
6 Sept 2026, 14:001,222-19
2 Sept 2026, 00:461,241+222
29 Aug 2026, 18:451,019+180
29 Aug 2026, 05:00839first reading

Engagement

20 posts held, back to 5 June 2026the 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.

ERR · 30 days
23.8%
avg views ÷ 1,209 subscribers
Avg views / post
288
4 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
4
of 20 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 1 of 4 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 August 2026
Posts held20 (5 June 202629 August 2026)
Views total1,151
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 05:00 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
10s
Average length
10s

Measured directly from 1 video 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

15 reactions across 6 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
15100.0%

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

Measured over the 20 most recent posts we hold, published 5 June 2026 to 29 August 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

29 Aug 2026, 04:00 UTC153 views0 reactionsread 29 August 2026
Photo

🎰 🎉成都学院祝同学们天天开心🎉 📮 参与条件: 🎫 加入-南栀的后花园 🎫 加入-成都学院(中转群) └ 🔑 发送口令﹝天天开心﹞ 🎫 加入-成都学院 🎫 加入-成都学院已验证老师精选车库 🎫 加入-Doctor的诊断记录 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 南栀 单P 白嫖券 × 1 ⚠️ 抽奖说明: ❗️无用户名、炸号、中奖后退出群组或频道不予兑奖; ❗️中奖后需要在48小时内联系兑奖人兑奖,过时不兑换,不能转让; ❗️开奖前在成都学院已验证老师精选车库有点赞和评论记录才能兑奖; 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年09月01日 12时00分00秒

27 Aug 2026, 07:08 UTC350 viewsread 29 August 2026

【妹子花名】:#南栀 【妹子账号】:@nanzhi520a 【验证留名】:李易峰 【验证时间】:8.26 【所在位置】:昭觉寺 【修车水费】:600 【是否代聊】:自聊 【身高身材】:小只 【妹子年龄】:20左右 【湿度紧度】:润 【颜值相似】:9分像吧 【凶器罩杯】:B 【环境卫生】:干净整洁 【服务内容】:菜单 【机车行为】:无 【优点缺点】:身材好,配合度高,女上很棒 【 性 价 比 】:价格是否符合整体体验感受 9分/ 满分10.0分 【推荐程度】:9分/满分10.0分; 评分标准 6分为及格,7分为良品(考虑价格可以看一看),8分(值得价格并且建议体验),9分(实为该价位中少见的精品),10分(极品) 【个人发挥】:南栀这里性价比挺高的,对颜值身材有挑剔的可以来试试。跟妹妹🐍的时候很爽,舌头交织在一起时滑润甜蜜,do i时妹妹很配合,女上动的很卖力,很会给你抛媚眼然后一顿猛夹,还好妹妹那天没找到🐢头敏感位置,不然肯

27 Aug 2026, 04:59 UTC325 viewsread 29 August 2026
Photo

今天开的哦 哥哥们 下午还有位置可以预约哦😘😘😘

27 Aug 2026, 04:29 UTC323 viewsread 29 August 2026

【妹子花名】:南栀 【妹子账号】:@nanzhi520a 【验证留名】:xitoe 【验证时间】:8.16 【所在位置】:昭觉寺 【修车水费】:6p 【是否代聊】:自 【身高身材】:160 【妹子年龄】:21 【湿度紧度】:紧度还行 【颜值相似】:8.5 【凶器罩杯】:C 【环境卫生】:整洁 【服务内容】:常规三件套 【机车行为】:不催 【优点缺点】:口的很好。教室环境有点差 【 性 价 比 】:价格是否符合整体体验感受 8.5分/ /满分10.0分 【推荐程度】:8.5分/满分10.0分; 评分标准 6分为及格,7分为良品(考虑价格可以看一看),8分(值得价格并且建议体验),9分(实为该价位中少见的精品),10分(极品) 【个人发挥】:吃饱饭无聊,无处可去,饱暖思淫欲联系ls,提前跟ls说迟到5分钟再到,ls没意见,快马加鞭冲去ls的教室,ls遥控进门,一进门见到小只马ls座在沙发玩手机,心中有个念头想像电影桥段那样直接冲

12 Aug 2026, 06:20 UTC≈3,320 views0 reactionsread 29 August 2026
Photo

今天开的哦哥哥们 还有位置可以预约哦😘😘

11 Aug 2026, 14:15 UTC≈2,060 views3 reactionsread 29 August 2026
Forwarded from @GZGDGS666Photo

#成都 #御姐 #小蛇 #精品 【怪獣の名】#南栀 【奧特の名】#戴拿 【怪獣の牌】@nanzhi520a 【怪獣の價】600/P 【怪の硬件】人照相似度能达到9以上,颜值挺不错,五官立体妆容精致。155/80御姐脸萝莉身,肤色偏黄,皮肤状态很不错,滑溜。 罩杯对B奶嘴褐色;腰上一点小肚子应该是湿气重导致的;屁股蝴蝶臀很翘但少了点点肉;酒杯腿比例好但不长。 户型方面:毛量正常,一线天。 【怪の軟件】态度还OK,能看出来是i人比较害羞不晓得怎么聊天,慢慢熟悉后会好点。很配合听指挥,特别会调琴~口活真心不错,而且口得特别久! 昆感方面:紧度适中、湿度适中、温度中上、反馈度中上。女上老猛了,可惜就是体力差点点~ 【玉玉の足】35吗埃及脚!又小又嫩,妥妥的可食用级别! 【奧特总结】御姐脸萝莉身,6米打卡完全不亏。 点赞100评论50发福利视频! 光之國の故事 https://t.me/GZGDGS666

3

6 Jul 2026, 05:09 UTC≈3,340 views4 reactionsread 29 August 2026

【妹子花名】:#南栀 【妹子账号】:@nanzhi520a 【验证留名】:Jerry 【验证时间】:07.05 【所在位置】:昭觉寺 【修车水费】:6P 【是否代聊】:自聊 【身高身材】:挺拔 小小只 【妹子年龄】:20左右 【湿度紧度】:热润紧 【颜值相似】:9分像吧 【凶器罩杯】:B吧 【环境卫生】:小区一般 房间还行 【服务内容】:菜单上的都有 【机车行为】:无 【优点缺点】:身材不错 很挺拔 【 性 价 比 】:价格是否符合整体体验感受 9分/ 满分10.0分 【推荐程度】:9分/满分10.0分; 评分标准 6分为及格,7分为良品(考虑价格可以看一看),8分(值得价格并且建议体验),9分(实为该价位中少见的精品),10分(极品) 【个人发挥】: 有一段时间没有cj了,这次选择了南栀妹妹,约到了头课,虽然等待了一会,但是和妹妹沟通非常顺畅,也比较有耐心。 开门见到了一位穿着紧身衣热裤妆容精致的妹妹,好身材一览无余,学院

4

4 Jul 2026, 10:22 UTC≈2,550 views0 reactionsread 29 August 2026

【妹子花名】:#南栀 【妹子账号】:@nanzhi520a 【验证留名】:xitoe 【验证时间】:7.3 【所在位置】:昭觉寺 【修车水费】:6P 【是否代聊】:自聊 【身高身材】:160 【妹子年龄】:21 【湿度紧度】:水多多 【颜值相似】:8.5很像 【凶器罩杯】:b+ 【环境卫生】: 房间靓 【服务内容】:常规服务 【机车行为】:无 【优点缺点】:还可以 【 性 价 比 】:价格是否符合整体体验感受 9分/ /满分10.0分 【推荐程度】:9.5分/满分10.0分; 评分标准 6分为及格,7分为良品(考虑价格可以看一看),8分(值得价格并且建议体验),9分(实为该价位中少见的精品),10分(极品) 【个人发挥】: 今天周六约的其他老师都没回复,有幸约到南栀老师身感欣慰。 约的16点,下午办完事后,飞车出击过来老师这边。通过老师的指引走了大概5分钟找到楼下,告诉妹妹,然后遥控上楼。 进门以后妹妹已经梳妆打扮好了,开门基

2 Jul 2026, 15:04 UTC≈1,440 views2 reactionsread 29 August 2026
Forwarded from @Doctor9527CJRebirth

Posted without readable text

2

1 Jul 2026, 06:35 UTC≈1,960 views0 reactionsread 29 August 2026

【妹子花名】:南栀 【妹子账号】:@nanzhi520a 【验证留名】:stupid 【验证时间】:7.1 【所在位置】:成华区 【修车水费】:6p/1000pp 【是否代聊】:本人 【身高身材】:160左右 【妹子年龄】:20左右 【湿度紧度】:很紧很湿 【颜值相似】:9.5分相似度 【凶器罩杯】:B 【环境卫生】:干净整洁 【服务内容】:课表上的都有 【机车行为】:无 【优点缺点】:大蟒蛇,乖巧配合,说话温柔,无机车行为。 【 性 价 比 】:这个价位性比不错 【推荐程度】:9分/满分10.0分; 评分标准 6分为及格,7分为良品(考虑价格可以看一看),8分(值得价格并且建议体验),9分(实为该价位中少见的精品),10分(极品) 【个人发挥】:进门看见妹妹小家碧玉的样子甚是可爱,与照片资料没有多少出入,赶紧洗漱上战场。妹子细枝挂硕果,但弹性足够,手感好!服务到位,全程微笑,配合度也高,情绪价值给得到位,女上太猛了,搞几下就射

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“南栀的后花园” (@nanzhi1314), 1,209 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/nanzhi1314.

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.