Channel
@gzmiabg
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
570subscribers
+13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002051396454 |
|---|---|
| Type | Channel |
| Username | @gzmiabg |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/gzmiabg |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 04:39 | 570 | +12 |
| 8 Aug 2026, 03:35 | 558 | no change |
| 7 Aug 2026, 15:22 | 558 | +1 |
| 7 Aug 2026, 13:30 | 557 | first reading |
20 posts held, back to 31 July 2025 — 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 pageof 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (31 July 2025 – 6 August 2026) |
| Views total | 478 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 03:35 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.
80 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 93.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 75 | 93.8% | |
| 👍 | 2 | 2.50% | |
| 👎 | 1 | 1.25% | |
| 💔 | 1 | 1.25% | |
| 🥰 | 1 | 1.25% |
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 17 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 80reactions 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 31 July 2025 to 6 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.
#米娅 #米粒 #联系方式：@miamiyakf #验证人: #dx #颜值评分:8/10 #身材评分:9/10 #情绪价值:10/10 #课表内容:10/10 #英雄类型: #配合敏感 #验证时间：2026-8-3 #优惠信息：499 #综合评分:9.5/10 #细节内容: 在校一本大学生暑期兼职，超敏感+主动迎合=无敌体验，自己摇高潮五次，大腿后侧手感柔软，颜值虽然中上，但是那个反馈一看就是素人，无脑冲。以下是正文，进门mm非常礼貌的问哥哥好，我寻思这妹妹好像放的挺开，坐旁边一会儿先漱口，马上窝到怀里，一进怀里，哎呦喂，羞涩起来了，瞬间勾起了我调戏她的心思，这捏捏，那挠挠，结果越缩靠越紧，自己还紧张起来了，这种反应不是假的，一看就是没经历过人事儿，一问，果然没谈过恋爱，兄弟们，轻点蹬，我还要返。 #温馨提示: MMK体验与诸多因素有关，本报告仅供参考，请理性选择，切勿对号入座 #报告审核: @IG_R…
#米娅 #小芸 #联系方式：https://t.me/gzmia #验证人:@kotohanon #颜值评分:10/10 #身材评分:10/10 #情绪价值:100/10 #课表内容:10/10 #英雄类型:#乖巧型＃可爱型 # 主动型#配合型 #验证时间：8.2 #综合评分:10/10 #细节内容:第一次去，地址有点出乎意料，还以为会是公寓什么的，不过环境还不错，芸神性格很好，很主动（被主动亲了好几次😌），摸起来很舒服，肉肉的，统共就去过两次，这次是体验感最好的一次，感觉以后也不会超越了😇，喜欢抱着芸神睡觉，感觉很安心，很安稳，非常舒服。简直就是神来着。ps.芸神很怕痒😋
#米娅 #小佳 #联系方式：https://t.me/gzmia #验证人:yankong #颜值评分:8/10 #身材评分:8/10 #情绪价值:10/10 #课表内容:10/10 #英雄类型:#乖巧型 ＃可爱型 # 配合型 #验证时间： #综合评分:10/10 #细节内容:进来坐下之后，还没怎么聊天，小佳仿佛看出了我的思念。小佳开始主动靠近，开始和我贴贴，慢慢的就亲吻在了一起，双手渐渐的搂住......湿吻，热吻，舌吻，坐着，靠着，躺着，心从火热到平静再到火热。我全程按耐不住，小佳非常懂我意思，进攻感十足，若即若离，挑逗着我的神经，眼神迷离，十分陶醉。总的来说，喜欢这种女友感，情绪价值满满的感觉再加上适当的亲热，真是一次完美的恋爱体验，会返
#米娅 #馨子 #联系方式：https://t.me/gzmia #验证人:匿名 #颜值评分:10/9 #身材评分:10/9 #情绪价值:10/7 #课表内容:10/7 #英雄类型: # 甜妹型 # #验证时间：6.26 #综合评分:10/10 #细节内容: 馨子真人是校园女神的感觉，身材不用说了，165cm的个子，细长腿，腿可以玩一年，全身是那种苗条身材，真的是又白又滑，出乎意料的是脸也是女神脸。🐍很配合，很软很甜，真的有种跟校花恋爱的感觉，最重要两个白兔，又滑又香，真的是亲了还想亲，女孩性格和善，配合性选手，不好的就是馨子不会主动找话题，总体上这次来还是值得的，馨子爱电竞，同样爱好者会有不少话题。
❤1
【秋名山 夜跑】 #女仆私影 #米亚 #企鹅 #车手： 滨州J（口袋） #联系：@miamiyakf #位置：#天河上社 #加油费用：499-100 #验证时间：2026-5-7 #优惠信息：D群减100 #颜值评分：8.0 #身材评分：7.5 #环境评分：8.5 #课表评分：8.0 #路况记录： 中了老朋友米亚的优惠券，不得不出击一下了，看到当天企鹅的舞蹈小视频，我嘞个豆，这不是妥妥白幼瘦萝莉吗！下班冲冲冲！过去也就打车5分钟到了，近得很。 进门就看到一个穿粉色衣服的小妹妹在沙发上坐着，挺乖巧来着。 【外貌服装】企鹅今天穿的是小粉色jk，白色卡哇伊的丝袜，身高还是有1米6的，本人和视频相比，7成像吧，没有特别小只。皮肤不错，也是很紧的。脸上胶原蛋白嫩嫩的，今年才刚大一，去年还是在校高中生噢。 【课表内容】进门之前店长嘱咐这妹妹舌吻方面可能不能是大蟒蛇类型。我疑问？摁？我是大蟒蛇客人吗？课…
❤10
#米娅 #依依 #联系方式：https://t.me/gzmia #验证人:ez2182 #颜值评分:10/10 #身材评分:10/10 #情绪价值:10/10 #课表内容:10/10 #英雄类型: # 御姐型 # 主动型 #验证时间：5.1 #综合评分:10/10 #细节内容: 依依很会聊天和我很聊得来 和她聊天超级有情绪价值 从籍贯性格星座都是我的天菜 妆容和穿搭都很有品 特别是身材还有腿型很戳我xp我好喜欢🥰 抱起来特别舒服 狠狠的沉船了
❤1
#米娅 #馨子 #联系方式：https://t.me/gzmia #验证人: 甜雪快跑 #颜值评分:10/9 #身材评分:10/8 #情绪价值:10/8 #课表内容:10/8 #英雄类型:#气质型 ＃清纯 #验证时间：2025-4-12 #综合评分:10/9 #细节内容: 看照片是我喜欢的类型，很难约到终于约到了，估计来得很少次数，报告也很少，不知道怎麽样。地址也好找，交通方便，到地方按要求上楼，是在会所楼上，安全性应该还行，一带我进房间，还不错挺大的，环境比某些好多了。小哥进来收了费，说助教在化妆，到房间坐了5分钟就安排进来了，等下进来果然没错颜值确认很对胃口，身材也不错，喜欢苗条的兄弟有福了，走在街上回头率很高，白色短裙青春靓丽，很有活力的感觉，一开始聊天看电影，聊天聊着聊着就进入主题了，可能是做助教不久，配合类型，会积极的配合，不会特别主动，可能不知道要干啥，需要彦祖们调教了，这些都是小问题，在广州硬件来说不错，青涩…
❤3
【海味报告】[https://t.me/longtnosea] 【所在地区】#天河 #棠下 【老师艺名】#小芸 #米娅 【上课费用】报告后469 【颜值分数】8 【身材分数】8 【服务内容】9 【服务态度】9 【推荐程度】9 【体验细节】 看到别人有推荐萝莉系的幻神我就马上出发了，约了头钟，小芸也非常准时来到了，小芸跟其他萝莉系不一样，是那种比较肉感的，不像是那种筷子腿之类的，我比较喜欢这种类型的，因为摇起来感觉好一点，小芸的情绪价值也给的很足，发现我是新手还主动引导我，全程玩得很开心，果然还是很年轻的女孩子玩比较开心呀，活力满满的样子真的很棒，孩子很喜欢，强烈推荐！ ♥️温馨提示: 以上仅代表个人体验,报告仅供参考！ 👉👉获取联系方式：@Doraemon01_Bot 👉👉报告提交发给: @jingxiang001bot
❤1
#米娅 #小芸 #联系方式：https://t.me/gzmia #验证人: #匿名 #颜值评分: 8/10 #身材评分: 7.5/10 #情绪价值: 8/10 #课表内容: 8.5/10 #英雄类型: 可爱型 #验证时间：2026-04-10 #综合评分: 8 #细节内容: 看了一些小芸的报告，和一些ootd，感觉蛮复合我的胃口，联系客服出击。 初见小芸，活泼开朗，热情好动，身材肉感有弹性。 课表内容方面，能蛇饱，后续解开bra，胸是对a，反补和yyc也有。 推荐萝莉控和蛇党。 ❤️报告仅供参考，个人体验因人而异！
❤1
#米娅 #小芸 #联系方式：https://t.me/gzmia #验证人:番茄 #颜值评分:8.7/10 #身材评分:8/10 #情绪价值:9/10 #课表内容:10/10 #英雄类型:#乖巧型 ＃可爱型 #验证时间：2026-4-10 #综合评分:10/10 #细节内容: 第一次去米娅 所以就只点了一小时，刚见到小芸的时候眼前一亮，少萝王。身材标准萌妹。是需要主动找话题的类型，所以刚开始有点拘谨，后面聊了一会就放开了，给人的感觉像学妹。情绪价值给的很满，会主动补钙。放开之后就开始狂🐍。小芸真的很主动。细节就不说了，适合喜欢身材娇小和喜欢甜妹的。
❤1
#米娅 #依依＃汤圆 #联系方式：https://t.me/gzmia #验证人: 牛局长 #颜值评分:9/10 #身材评分:9/10 #情绪价值:9/10 #课表内容:9/10 #英雄类型:#御姐型 ＃配合型 #验证时间：2025-4-04 #综合评分:9/10 #细节内容:好不容易回来，必须给自己整点好的啊，也是很久没去米娅了必须帮衬一下，看着出勤表上琳琅满目不知道选什么好，店长就给我推荐了依依和汤圆，和店长聊了一会后进入房间，店长还记得雪糕的约定（这必须点赞昂）稍作一会之后依依就来啦，依依身穿黑色裙子，她一进的时候这身高这身材这大长腿我是真的喜欢啊，她坐在我旁边靠着我，她的大腿放在我腿上，我边摸边聊天🥰，聊着聊着自己手缓缓摸向她的胸部，我缓缓靠近她的唇，注视着她，舌头伸进她的口中搅动，在嘴里翻江倒海，在河倾海覆，在享受，在沉浸，在感受她的琼浆甘露，随后我缓缓掀开她的衣物，舔舐她的樱桃，依依也十分的配合，口中也发出请问叫声…
❤3👍2
#米娅 #馨子 #联系方式：https://t.me/gzmia #验证人: 5lay Mong #颜值评分:10/10 #身材评分:10/10 #情绪价值:10/10 #课表内容:10/10 #英雄类型:#乖巧型 ＃可爱型 #验证时间：2025-2-01 #综合评分:10/10 #细节内容: 之前看了好久出勤，一直没有来，然后看见发的馨子颜值很对胃口，就想着联系了来试一试，这客服一直叫我宝宝还以为是女孩子呢，原来是小哥哥太坏了，一带我进房间就看见了一个身材很不错的小妹妹坐在沙发上，小哥进来我就问了问那个是馨子吗，果然没错颜值身材确认很对胃口，到房间坐了3分钟就安排进来了，馨子有点羞涩感，会害羞哈哈哈哈太有趣了，颜值真的很能打，身材也很好，一开始互相了解了一下，就进入主题了，偏配合类型，会积极的配合，可能没做多久的原因，不会特别主动，这些都是小问题颜值身材属实太对胃口了，刚刚来没多久能如此配合我已经非常知足了所，不能太完美…
❤6
Showing the 12 most recent of 20 posts we hold for @gzmiabg. 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 — 862,322 of 1,481,502entries 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“广州MIA米娅MMK报告馆” (@gzmiabg), 570 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/gzmiabg.
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.