上海【喜茶】作业报告 👧艺名: #念念 ⛳位置: #浦东 申城佳苑 🤖课表: https://t.me/xichalssh/27477 📒小作文: 念念老师人照一致,资料属实。过程积极配合,换了好几个姿势,服务很多,声音反馈自然,体验感不错,一次性用品充足。有女友感,会复刷 💁反馈人: Lisette

Channel
(上海)念念的花园
@niannian_huayuan
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,445subscribers
-1,523 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 | -1002839729856 |
|---|---|
| Type | Channel |
| Username | @niannian_huayuan |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/niannian_huayuan |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 04:40 | 2,445 | -9 |
| 12 Sept 2026, 07:59 | 2,454 | -3 |
| 7 Sept 2026, 23:21 | 2,457 | +174 |
| 2 Sept 2026, 13:14 | 2,283 | +44 |
| 30 Aug 2026, 22:25 | 2,239 | -20 |
| 27 Aug 2026, 13:12 | 2,259 | -80 |
| 24 Aug 2026, 03:52 | 2,339 | -101 |
| 20 Aug 2026, 17:29 | 2,440 | -648 |
| 17 Aug 2026, 22:05 | 3,088 | -671 |
| 14 Aug 2026, 14:05 | 3,759 | -449 |
| 11 Aug 2026, 05:35 | 4,208 | +314 |
| 8 Aug 2026, 14:05 | 3,894 | -74 |
| 7 Aug 2026, 18:02 | 3,968 | no change |
| 7 Aug 2026, 17:48 | 3,968 | first reading |
Engagement
21 posts held, back to 27 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 3 pages 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 21 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 49s
- Average length
- 12s
Measured directly from 4 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.
Reaction mix
5 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 100.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 6 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 5 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 27 July 2026 to 8 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
开课了可约🥰😄
撸猫猫😀
❤1
https://t.me/shxyls/29407?single
❤1
(上海)念念的花园 pinned a photo
🎰 🌈 #浦东 #念念 @niannianpudong 夏日奶茶红包 📮 抽奖条件: 🎫 加入-(上海)念念的花园 🎫 加入-魔都 探花/验证/自聊/选妃/榜单/评价/报告 🎁 奖品内容: 夏日奶茶红包🧧18 × 2 💡 活动说明: 🌟愿中奖的哥哥,在Cj路上,捧起手上的奶茶,能想起在 #浦东 还有 #念念 在等你。 🌟中奖后 找 @niannianpudong 领取 🌟祝魔都探花的哥哥们在CJ路上一帆风顺 📅 开奖日期:(UTC+8) 2026年08月12日 12时00分54秒
老师:念念 @niannianpudong 评分:9.0分 评价:提前约的念念老师的课,这个天还真热,到点去的时候老师已经提前开好了空调,进屋凉嗖嗖的,挺爽。第一眼看念念老师身高应该在1米六左右,身材不错。交完水费,沐浴进房间办正事。大约15分钟的样子,今天状态还算不错,差点好几次就控制不住要出货了,归根结底就是念念老师的服务太到位了,勾的我欲火焚身,哈哈。完事后又在床上靠着休息了一会,聊了一会天,看看时间差不多了,主要待会还有事,必须得走了,总体体验挺好的,应该还会复刷👍 反馈人:待滚的羔羊 魔都探花男群:https://t.me/+mhw016G0xDo0ZWI1
开课啦🥰可约
今日课满,可约明日❤️ 滴滴滴😘
上海【喜茶】作业报告 👧艺名: 念念(点击查看) 🆔联系: @niannianpudong ⛳位置: #浦东 申城佳苑 📒小作文: 地点张江,小区住宅环境就是一般的住宅,装修一般。正常,停车方便,念念老师真人和照片差别不大,人照8分吧。身材不错,服务态度各方面挺好的,该做的都会给你做到位,这个价格性价比算挺好了吧,可以推荐。 💁反馈人: Alban 标签: #念念 #浦东 #御姐
抽奖浦东念念 @niannianpudong 口令红包抽奖活动(编号L178523693694)已成功开奖: 创建人:叮当猫[6964232154] 已参与人数:1812 中奖名单如下: 年少无*[69917424**](奖品为18元口令红包) 一卷成*[71947436**](奖品为18元口令红包) 黄*[83204409**](奖品为18元口令红包)
(上海)念念的花园 pinned «https://t.me/xichafuli/1625»
Showing the 12 most recent of 21 posts we hold for @niannian_huayuan. 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 7 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.
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.
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.
“(上海)念念的花园” (@niannian_huayuan), 2,445 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/niannian_huayuan.
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.