Telegram RegisterThe public register of Telegram
Telegram profile photo for 南京 品茶 ✈️资源

Channel

南京 品茶 ✈️资源

@nanjingziyuan1

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

23subscribers

+0 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001630114242
TypeChannel
Username@nanjingziyuan1
CreatedBetween 1 December 2021 and 2 November 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live19 September 2026
Measurements held2
On Telegramt.me/nanjingziyuan1

Growth

2311 Aug 2026, 22:52 — 23 subscribers11 Aug 2026, 23:00 — 23 subscribers11 Aug 2026, 22:5211 Aug 2026, 23:00
2 measurements taken within a single day. 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 22–24 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 23:0023no change
11 Aug 2026, 22:5223first reading

Engagement

9 posts held, back to 2 November 2022 — the 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 9 posts for this entry, the most recent from 27 July 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
558
Links
1

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

4 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤250.0%
👍250.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 3 of the 9 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 9 most recent posts we hold, published 2 November 2022 to 27 July 2023, 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

27 Jul 2023, 18:04 UTCviews —

南京 品茶 ✈️资源 pinned «以现在的最新模式为准👇👇👇👇👇👇👇👇👇👇👇👇 以最新资源为准!之前的所有频道作废👇 👉全国各地资源信息总频道👈 🇨🇳 北京市 上海市 广州市 深圳市 🇨🇳 重庆市 天津市 浙江省 山东省 🇨🇳 东北三省 【辽宁 吉林 黑龙江】 🇨🇳 苏 . 皖 【 江苏省 安徽省 】 🇨🇳 川 . 渝 【 四川省 重庆市 】 🇨🇳 陕 . 豫 【 河南省 陕西省 】 🇨🇳 晋 . 云 【 山西省 …»

24 Jul 2023, 11:48 UTC608 viewsread 11 August 2026

以现在的最新模式为准👇👇👇👇👇👇👇👇👇👇👇👇 以最新资源为准!之前的所有频道作废👇 👉全国各地资源信息总频道👈 🇨🇳 北京市 上海市 广州市 深圳市 🇨🇳 重庆市 天津市 浙江省 山东省 🇨🇳 东北三省 【辽宁 吉林 黑龙江】 🇨🇳 苏 . 皖 【 江苏省 安徽省 】 🇨🇳 川 . 渝 【 四川省 重庆市 】 🇨🇳 陕 . 豫 【 河南省 陕西省 】 🇨🇳 晋 . 云 【 山西省 云南省 】 🇨🇳 津 . 冀 【 天津市 河北省 】 🇨🇳 华东地区 【 福建省 江西省 】 🇨🇳 华中地区 【 湖北省 湖南省 】 🇨🇳 华南地区 【 广东 广西 海南 】 🇨🇳 西南西北以及其他地区 🇨🇳 …

11 Nov 2022, 02:30 UTC994 views3 reactionsread 11 August 2026
Photo

【寻欢地点】:鼓楼区 【信息来源】:狼友推荐.亲身体验 【服务项目】:69.指滑.胸推.臀推.冰火.毒龙.鸳鸯浴.漫游.口爆.舌吻.爱爱 【妹妹数量】:3 【妹妹年龄】:23 【环境设备】:干净舒适齐全 【营业时间】:兼职妹妹.加上自己约时间 【价格一览】:700全/1800夜 【安全评估】:100分 很隐蔽.安全可靠 【服务星级】:★★★★★ 【重点推荐】:胸大身材好水多听话粉嫩骚气

👍2❤1

7 Nov 2022, 07:17 UTC699 views0 reactionsread 11 August 2026
Photo

【寻欢地点】:南通市崇川区附近 【信息来源】:朋友推荐 亲身体验 【服务项目】:做爱 舌吻69毒龙SM 丝袜制服 口爆 全套 服务 【妹妹数量】:1 【环境设备】:公寓 【营业时间】:自己联系 【价格一览】:1000/120分钟 时间内不限次 全套服务 【安全评估】:评分,满分100。 【服务星级】:☆☆☆☆☆ 【重点推荐】:年轻会玩 服务好 配合好

7 Nov 2022, 07:16 UTC513 viewsread 11 August 2026
Photo

【寻欢地点】:雨山区康泰佳苑 【信息来源】:亲身体验 【服务项目】:口活 无套吹箫 69 口暴 漫游 过水 深喉 制服丝袜 【妹妹数量】:1 【环境设备】:小区,自己开房玩好点 【营业时间】:提前预约 【价格一览】:700P 1100PP 2000夜 【安全评估】:80 【服务星级】:★★★★★ 【重点推荐】:

7 Nov 2022, 07:15 UTC433 viewsread 11 August 2026
Photo

【寻欢地点】:江苏省份、南京城市(建邺区大概位置) 【信息来源】:狼友推荐、论坛、亲身体验 【服务项目】:鸳鸯浴,漫游,胸推,69式,冰火,口活,爱爱、SM(可选,勿必填写真实服务项目) 【妹妹数量】:1 【环境设备】:公寓 【营业时间】:自己约 【价格一览】:1000/次或1300天等 【安全评估】:评分,满分100。 【服务星级】:★★★★★(最高5星)应适当评价质量 【重点推荐】:最值得推荐的地方以供参考

2 Nov 2022, 02:34 UTC396 viewsread 11 August 2026
Photo

【寻欢地点】:苏州市姑苏区 【信息来源】:个人兼职 【服务项目】:鸳鸯浴,漫游,胸推,69式,冰火,口活,爱爱、SM 【妹妹数量】:3-5 【环境设备】:私密房间 【营业时间】:12:00~00 【价格一览】:700 【安全评估】:私密安全可靠 【服务星级】:★★★★★ 【重点推荐】:妹子服务特别好,不催懂配合

2 Nov 2022, 02:31 UTC355 viewsread 11 August 2026
Photo

【寻欢地点】:江苏省无锡市梁溪区水仙里小区 【信息来源】:狼友推荐、论坛、亲身体验 【服务项目】:洗吹做一条龙 毒龙 舔蛋 冰火 漫游 口爆 【妹妹数量】:1 【环境设备】:小区 【营业时间】:下午2点 【价格一览】:600全套 【安全评估】:安全 【服务星级】:★★★★★ 【重点推荐】:身材好

2 Nov 2022, 02:09 UTC293 views1 reactionsread 11 August 2026
Photo

【寻欢地点】:南宁 【信息来源】:狼友推荐 【服务项目】:鸳鸯浴,漫游,胸推,69式,冰火,口活,爱爱、SM 【妹妹数量】:1 【环境设备】:公寓也能外出 【营业时间】:自己约 【价格一览】:600/次或1000/2次1800包夜 【安全评估】:评分,97 【服务星级】:★★★★★ 【重点推荐】:骑乘,后入式,口活好,服务主动

❤1

Showing the 9 most recent of 9 posts we hold for @nanjingziyuan1. 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.

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

“南京 品茶 ✈️资源” (@nanjingziyuan1), 23 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/nanjingziyuan1.

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.