Channel
@gzmiamiya
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,542subscribers
+43 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002059977265 |
|---|---|
| Type | Channel |
| Username | @gzmiamiya |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/gzmiamiya |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 04:15 | 3,542 | +13 |
| 10 Aug 2026, 10:28 | 3,529 | +29 |
| 7 Aug 2026, 15:58 | 3,500 | +1 |
| 7 Aug 2026, 13:18 | 3,499 | no change |
| 7 Aug 2026, 12:56 | 3,499 | first reading |
9 posts held, back to 3 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 2 pagesof 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 4 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 9 (3 August 2026 – 7 August 2026) |
| Views total | 4,338 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:11 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.
6 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 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 4 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 6reactions 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 3 August 2026 to 7 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.
今日（8.8）周六5位妹妹在店哦 #广州 #天河 #MMK #女大 #恋爱 1.圆宝5点后可约 2.瑶瑶5点后可约 3.米粒5点后可约（7点8点🈳） 4.小芸6点后可约（7-9🈳） 5.小幼6点后可约 （具体预约时间以米亚客服沟通确认为准，好几个学校严随时预约不固定感谢宝宝理解，爱你🌹🌹🤗😘） 写报告还可叠加立减30 💰 预约请联系： tg：@miamiyakf wx： yirenwx1 聊天群： t.me/gzmia （入群联系客服） 报告馆: https://t.me/gzmiabg 地址：广东省广州市天河公园（点击即可导航）
今日（8.7）周五5位妹妹在店哦 #广州 #天河 #MMK #女大 #恋爱 1.圆宝5点后可约🈵🈵🈵 2.瑶瑶5点后可约 3.小芸6点后可约🈵🈵🈵 4.小佳6点后可约（10-12🈳 5.米粒6点后可约🈵🈵🈵 （具体预约时间以米亚客服沟通确认为准，好几个学校严随时预约不固定感谢宝宝理解，爱你🌹🌹🤗😘） 写报告还可叠加立减30 💰 预约请联系： tg：@miamiyakf wx： yirenwx1 聊天群： t.me/gzmia （入群联系客服） 报告馆: https://t.me/gzmiabg 地址：广东省广州市天河公园（点击即可导航）
幻神小芸明天6-12在线🌹🌹🌹
❤2
#米娅 #米粒 #联系方式：@miamiyakf #验证人: #dx #颜值评分:8/10 #身材评分:9/10 #情绪价值:10/10 #课表内容:10/10 #英雄类型: #配合敏感 #验证时间：2026-8-3 #优惠信息：499 #综合评分:9.5/10 #细节内容: 在校一本大学生暑期兼职，超敏感+主动迎合=无敌体验，自己摇高潮五次，大腿后侧手感柔软，颜值虽然中上，但是那个反馈一看就是素人，无脑冲。以下是正文，进门mm非常礼貌的问哥哥好，我寻思这妹妹好像放的挺开，坐旁边一会儿先漱口，马上窝到怀里，一进怀里，哎呦喂，羞涩起来了，瞬间勾起了我调戏她的心思，这捏捏，那挠挠，结果越缩靠越紧，自己还紧张起来了，这种反应不是假的，一看就是没经历过人事儿，一问，果然没谈过恋爱，兄弟们，轻点蹬，我还要返。 #温馨提示: MMK体验与诸多因素有关，本报告仅供参考，请理性选择，切勿对号入座 #报告审核: @IG_R…
❤1
今日（8.6）周四3位妹妹在店哦 #广州 #天河 #MMK #女大 #恋爱 1.圆宝5点后可约 2.瑶瑶5点后可约 3.小佳6点后可约 （具体预约时间以米亚客服沟通确认为准，好几个学校严随时预约不固定感谢宝宝理解，爱你🌹🌹🤗😘） 写报告还可叠加立减30 💰 预约请联系： tg：@miamiyakf wx： yirenwx1 聊天群： t.me/gzmia （入群联系客服） 报告馆: https://t.me/gzmiabg 地址：广东省广州市天河公园（点击即可导航）
❤3
今日（8.5）周三4位妹妹在店哦 #广州 #天河 #MMK #女大 #恋爱 1.依依5点后可约 2.圆宝5点后可约 3.瑶瑶5点后可约 4.小佳6点后可约 （具体预约时间以米亚客服沟通确认为准，好几个学校严随时预约不固定感谢宝宝理解，爱你🌹🌹🤗😘） 写报告还可叠加立减30 💰 预约请联系： tg：@miamiyakf wx： yirenwx1 聊天群： t.me/gzmia （入群联系客服） 报告馆: https://t.me/gzmiabg 地址：广东省广州市天河公园（点击即可导航）
Photo, posted without a caption
#米娅 #小芸 #联系方式：https://t.me/gzmia #验证人:@kotohanon #颜值评分:10/10 #身材评分:10/10 #情绪价值:100/10 #课表内容:10/10 #英雄类型:#乖巧型＃可爱型 # 主动型#配合型 #验证时间：8.2 #综合评分:10/10 #细节内容:第一次去，地址有点出乎意料，还以为会是公寓什么的，不过环境还不错，芸神性格很好，很主动（被主动亲了好几次😌），摸起来很舒服，肉肉的，统共就去过两次，这次是体验感最好的一次，感觉以后也不会超越了😇，喜欢抱着芸神睡觉，感觉很安心，很安稳，非常舒服。简直就是神来着。ps.芸神很怕痒😋
今日（8.4）周二5位妹妹在店哦 #广州 #天河 #MMK #女大 #恋爱 1.依依5点后可约 2.瑶瑶5点后可约 3.小佳6点后可约 4.圆宝6点后可约 5.米粒6点后可约🈵🈵🈵 （具体预约时间以米亚客服沟通确认为准，好几个学校严随时预约不固定感谢宝宝理解，爱你🌹🌹🤗😘） 写报告还可叠加立减30 💰 预约请联系： tg：@miamiyakf wx： yirenwx1 聊天群： t.me/gzmia （入群联系客服） 报告馆: https://t.me/gzmiabg 地址：广东省广州市天河公园（点击即可导航）
Showing the 9 most recent of 9 posts we hold for @gzmiamiya. 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.
Citation-graph rank — 1,119,426 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“广州MIA米娅MMK恋爱馆” (@gzmiamiya), 3,542 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/gzmiamiya.
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.