Channel
@minahuayuan
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
35subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004375367977 |
|---|---|
| Type | Channel |
| Username | @minahuayuan |
| Description | 联系电报： @MNmina1 机器人号： @minaduoduoBOT 个人展示频道： https://t.me/minahuayuan |
| Created | Between 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 1 |
| On Telegram | t.me/minahuayuan |
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 14:22 | 35 | first reading |
10 posts held, back to 19 September 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.
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 2 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 19 September 2026 |
|---|---|
| Posts held | 10 (19 September 2026 – 19 September 2026) |
| Views total | 1,721 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Sept 2026, 14:22 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.
Lifetime counters from Telegram’s own channel header, read 19 September 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.
Measured directly from 3 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.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 2 of the 10 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 19 September 2026 to 19 September 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.
奶茶妹报告模版： telegram.me/+iSwJ-vAcG902N2E1 【茶妹艺名】 【联系方式】米娜 @MNmina1 【所在位置】：#浦东 【上课茶费】： 工兵 【验证留名】：张小天 【验证时间】：9.19 【人照几成】：8 【服务态度】： 【体验评价】： 【服务过程】：见面人和照片一差不多吧，参考第二张图拿扇子那张，身材不错，胸的手感很好。这是长处吧，至于其他的，就没了。 【温馨提醒】：报告仅供参考， 注：提交报告需要约课记录
https://t.me/shsfdagbt
🌷我在【上海栖心地】工兵上榜了🌷 https://t.me/SHqixindi 🌷每日免费拿 【半价、红包】优惠🌷 更有【抽奖 白嫖 现金红包】等着你 🌷上海栖心地榜单🌷 https://t.me/SHqixindi_bangdan 🌷上海栖心地报告区🌷 https://t.me/SHqixindibaogaoqu 🌷上榜管理： @SHqixindi_Guanli_bot🌷
转发此条信息到频道 上海修车泡泡屋福利群： 免费拿 【半价、六折】优惠 更有【抽奖 白嫖 现金红包】等着你 免费上榜管理： @shpaopaowubot 福利交流群 https://t.me/shpaopaowujlq 泡泡修车榜单 https://t.me/shpaopaobd 报告区 https://t.me/shpaopaowubgq
📊 0条车评，综合评分 好评 0% |人照 |服务 中评 0% |颜值 |态度 差评 0% |身材 |环境 模特艺名：米娜 模特地区：浦东新区 模特资料：19 163 45 C 拍摄费用：10p 18pp 模特电报：@MNmina1 模特频道：https://t.me/minahuayuan 通过此链接评价： https://t.me/shxcxw_bot?start=commentTeacher-TE178979792187 查看详细资料： https://t.me/shxcxw_bot?start=teacherContact-TE178979792187 🔰 Powerd by 泡芙： 聊天群 上课群 作业榜 会员群（提交作业获取链接） 聊天群长期半价活动。
上海【蕉点】 🎟福利5折6折｜抽奖红包🧧 🎭蕉友男群 https://t.me/SHjdqun 🏆蕉点总榜 https://t.me/shjiaodian/1359 🥇好评榜单 https://t.me/shjdtop 🏆 蕉点蕉友群是极搜上海区排名第一群 (点击查看) 的真实活跃大群，有5w+真实蕉友，欢迎学长们加入！ ——————————————— 🍌上榜管理 @SHjiaoge
👍上海工兵福利群 ，福利易拿 💌榜上老师均已验证，放心出击 ✨上海修车社区【交流群】 ✨上海修车社区【轮播群】 ✨上海修车社区【公开榜】 ✨上海修车社区【报告区】 🧑💻群组管理： @bbsuh69_bot 🎁🎁群内不定时发放各种福利，发言积分可兑换半价优惠，大小红包，出击补贴等等
工作室环境照，环境很好的哦哥哥们。
🎉 浦东【米娜 @MNmina1】P/PP五折卷 🎁 奖品清单 • P/PP五折卷 × 1 🛡️ 参与条件 • 加入 上海修车协会 • 加入 TG中文导航搜索 • 加入 浦东米娜私密花园🌷 • 需消耗修车币：10 • 必须设置用户名 🔮 祝福加持 • 祝福消耗：50修车币 • 祝福上限：无上限次 • 祝福一次增加一个抽奖号，提高中奖率 • 幸运值祝福：支持 幸运值说明 ⌛ 抽选时刻 • 2026-09-22 12:40:00 📜 抽奖说明 刷屏、灌水、纯表情、复制粘贴、无意义对话、撤回内容等，一律视为无效发言，不计入统计！ 再次重申：灌水无意义发言都不兑奖！请用心交流。 活动最终解释权归上海修车协会管理团队所有。 中奖的联系 老师 约时间 工兵优惠出击必须写报告 24小时内预约时间，三天内出击，过时自动作废 炸号需找管理验证，无法验证，奖品放回奖池重新抽奖 中奖需本人出击不得转让， 中将联系：@MNmina1 ✨…
❤1
📊 0条车评 写报告 好评 0% | 人照 | 服务 中评 0% | 颜值 | 态度 差评 0% | 身材 | 环境 🥰 花名： #米娜 ✅ 状态：🟢 已验证 /【视频验证】 📍 地区位置：#浦东 🏠 场地：小区 ⬆️ 身高：163cm ⚖️ 体重：45kg 🎂 年龄：07 👙 罩杯：C 💰 价格：1000 /P （40分钟）1800 /PP（80分钟） #10/18 夜 ： 🔡时长： 🎯 服务标签：#舌吻 #69 #kiss #洗吹做 #陪浴 #制服丝袜 🔡 个人介绍： @MNmina1 双向：@minaduoduoBOT 频道： https://t.me/minahuayuan （老师简介） 新人妹妹初次下海，性格活泼，…
❤1
Showing the 10 most recent of 10 posts we hold for @minahuayuan. 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 5 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“浦东米娜私密花园🌷” (@minahuayuan), 35 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/minahuayuan.
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.