https://t.me/+u1jjCc-kVcc4MmFl https://t.me/+09O-UiL1t2lhYmQ1 https://t.me/+9depae96-xM2YmQ1 https://t.me/+2J8eJXjR1-UzMzJl 新增四公群 招收大口径👋拨团队 量大可拉专群
❤3
Signed (不在线 有事联系助理程程)无心

Channel
@nanyuyuan
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
15subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001696386308 |
|---|---|
| Type | Channel |
| Username | @nanyuyuan |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 7 October 2026 |
| On Telegram | t.me/nanyuyuan |
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 1 October 2026 and assigned it the closest of 31 fixed categories, at 62% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 23:58 | 15 | -1 |
| 11 Aug 2026, 21:30 | 16 | no change |
| 7 Aug 2026, 12:12 | 16 | first reading |
18 posts held, back to 12 February 2024 — 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 18 posts for this entry, the most recent from 24 September 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 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.
98 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 87.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 86 | 87.8% | |
| 👍 | 5 | 5.10% | |
| 🐳 | 2 | 2.04% | |
| 👎 | 2 | 2.04% | |
| 🤮 | 2 | 2.04% | |
| 💩 | 1 | 1.02% |
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 16 of the 18 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 98 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 12 February 2024 to 24 September 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
https://t.me/+u1jjCc-kVcc4MmFl https://t.me/+09O-UiL1t2lhYmQ1 https://t.me/+9depae96-xM2YmQ1 https://t.me/+2J8eJXjR1-UzMzJl 新增四公群 招收大口径👋拨团队 量大可拉专群
❤3
Signed (不在线 有事联系助理程程)无心
达利888 完美谢幕
❤4
Signed 无心
新上押俩达利公群 https://t.me/+EPJtstnyFgczN2Jl https://t.me/+MMKOoyTXYfA1YjZl
❤3
Signed 无心
干就完了!
Signed 无心(招👋拨大口径团队)
诚招手拨团队 在押公群有新币2113 汇旺9733 达利1433 达利888 达利2908 虎牙678等公群 总押超三万u 实力老板带量来谈 可拉场地直接打 你有量我有价 一定会给各位一副满意答卷!
❤6🐳2
Signed 无心(👋拨团队联系)
无心の日记 pinned Deleted message
https://t.me/+ErGuudi7DOM2NDhl 新增公群 新币2113
❤8
Signed 无心
无心在押公群 现总押1️⃣7️⃣0️⃣0️⃣0️⃣💰 币安5000u: https://t.me/+1zwDsi3kJNc5NDAx 永盛2000: https://t.me/+pL0ITik7HpU0OTUx 达利5000: https://t.me/+bKYbrzmOurY4MTRk 虎牙5000: https://t.me/shequn9 请大家放心做单!押金管够 本人隶属安迪集团旗下 手拨老玩家!
❤5👍3💩1
Signed (度蜜月中 有事联系特助得力)无心
我投降 关于你的我都退让
❤4
https://t.me/+bKYbrzmOurY4MTRk 安迪集团 诚招代理 虎牙666 达利1433等公群 有意者联系 @nanyuxin 全部平放 直接拉场地群
❤6
后来我开上了保时捷 但还是没能追回你的心
❤6👍1
穿上的是AJ 追不上的是你
❤6🤮2
Showing the 12 most recent of 18 posts we hold for @nanyuyuan. 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.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“无心の日记” (@nanyuyuan), 15 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/nanyuyuan.
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.