Channel
@naif0867
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,118subscribers
+2,443 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004377449578 |
|---|---|
| Type | Channel |
| Username | @naif0867 |
| Created | Between 1 June 2026 and 17 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/naif0867 |
Giveaways & airdrops — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 03:04 | 3,118 | +144 |
| 3 Nov 2026, 06:39 | 2,974 | -136 |
| 31 Oct 2026, 17:05 | 3,110 | +542 |
| 28 Oct 2026, 12:22 | 2,568 | +408 |
| 25 Oct 2026, 06:16 | 2,160 | +631 |
| 22 Oct 2026, 10:56 | 1,529 | +100 |
| 19 Oct 2026, 00:36 | 1,429 | -6 |
| 15 Oct 2026, 19:41 | 1,435 | -14 |
| 12 Oct 2026, 10:41 | 1,449 | -96 |
| 5 Oct 2026, 10:01 | 1,545 | -11 |
| 27 Sept 2026, 10:02 | 1,556 | +568 |
| 14 Sept 2026, 10:01 | 988 | -12 |
| 11 Sept 2026, 03:17 | 1,000 | -66 |
| 6 Sept 2026, 15:21 | 1,066 | +8 |
| 2 Sept 2026, 08:14 | 1,058 | +283 |
| 26 Aug 2026, 01:57 | 775 | +100 |
| 25 Aug 2026, 16:00 | 675 | no change |
| 25 Aug 2026, 15:45 | 675 | first reading |
20 posts held, back to 17 August 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 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 20 posts for this entry, the most recent from 25 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 6 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.
7 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 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 5 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 7 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 17 August 2026 to 25 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.
🎉 联邦~桂城萘菲学妹💃🏻福利抽奖🎰 🎁 奖品清单 • 1P半价 × 1 • 1P优惠100 × 5 • 2P优惠200 × 3 • 18.8元奶茶🧋红包 × 5 📢 参与条件 • 加入 广州佛山联邦出击群（重生版） • 加入 奈菲学妹的花园 • 加入 广州佛山邦女郎动态榜 • 加入 广州佛山联邦老师榜 • 加入 广州佛山联邦老师打卡群 • 加入 广州佛山联邦抽奖榜 • 需消耗奔周能量：3 ⌛ 开奖时间 • 2026-08-28 22:00:00 📜 抽奖说明 萘菲学妹：https://t.me/Gzffol/43520 1，本活动由萘菲学妹老师赞助,私聊 @Naifei81 兑奖。 2，开奖后请老师七天内兑券，转让需老师同意。 3，中半价券先拉黑抽奖30天，出击交报告即解。 ✨ 愿好运常伴大家，祝大家好运！点击下方按钮参与抽奖。
❤1
奈菲学妹的花园 pinned a photo
🎰 【车友会】桂城·萘菲🦋抽奖活动🎁 📮 抽奖条件: 🎫 加入-佛山车友会 🎫 加入-佛山车友会公开榜 🎫 加入-车友会抽奖频道 🎫 加入-奈菲学妹的花园 🎟️ 要求活动期间群内发言数 5 🍀 每5分中奖几率加1倍 ⤷在群中输入「喜+1」 🎁 奖品内容: P半价优惠卷 × 1 爱心奶茶🧋￥：18.8🧧 × 5 P100优惠卷 × 5 PP200优惠卷 × 3 💡 活动说明: 👉中奖联系: @Naifei81 👉炸号无效，兑奖限开奖后5天内 👉中奖机制: 车友会群内发“喜+5”可以加成 👉中奖半价卷者出击后需提交报告！未提交作拉黑处理！ 更多抽奖信息👉 https://t.me/CYHCJPD 🔥狼友避雷交流群(🈲老师、🈲广告)👉 https://t.me/+iwnlfkXaKfNkYTA8 📅 开奖日期:(UTC+8) 2026年08月30日 13时55分52秒
今天开课了哦学长们
Video, posted without a caption
Video, posted without a caption
身体不适哦，今天休息啦
【嫩妹报告】https://t.me/NNnmmtfzz 【老师艺名】萘菲学妹 【联系方式】@Naifei81 【所在位置】桂城 【验证留名】姐夫 【验证时间】5点 【修车费用】800 【颜值身材】9 【服务内容】写的都有 【服务态度】非常热情 【优点缺点】女友感 【推荐程度】10 【体验细节】 本人2刷萘菲学妹了，非常嫩，喜欢嫩妹都可以无脑冲，进门就笑脸迎人。和频道上的照片一模一样，非常有亲切感， 准备的很齐全，环境很舒服。洗澡的空间也很舒服，萘菲学妹挺自来熟的，聊天非常愉快。真的很舒服，口也没有齿感，能感觉出生疏，但是很尽力的吞吐，很舒服，这种态度非常好。床上就肯定是辣妹三件套，但是各种姿势非常配合，也没有不耐烦，屁股大后入非常爽，很紧很舒服，最重要的是课程安排的一点都不紧。虽然是兼职，但是方方面面体验感都很好，紧致度也可以，反馈的情绪也是非常到位，非常值得尝试。妹子下海不久,不奈撞，多调教。😂😂😂 ♥温馨提示: 以上…
https://t.me/baogaowenxue/9404
在开喔
https://t.me/baogaowenxue/9388
奈菲学妹的花园 pinned a photo
Showing the 12 most recent of 20 posts we hold for @naif0867. 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.
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.
Named by 10 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.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“奈菲学妹的花园” (@naif0867), 3,118 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/naif0867.
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.