Channel
@maodutanhua
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
6,172subscribers
+152 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002805625317 |
|---|---|
| Type | Channel |
| Username | @maodutanhua |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/maodutanhua |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 08:08 | 6,172 | +56 |
| 12 Aug 2026, 23:07 | 6,116 | +42 |
| 10 Aug 2026, 07:50 | 6,074 | +43 |
| 7 Aug 2026, 12:52 | 6,031 | +11 |
| 6 Aug 2026, 20:16 | 6,020 | first reading |
68 posts held, back to 5 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 9 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 13 of 68 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 68 (5 August 2026 – 11 August 2026) |
| Views total | 33,267 |
| Reactions total | 9 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03:33 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.
9 reactions across 8 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 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 13 of the 68 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 9reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 68 most recent posts we hold, published 5 August 2026 to 11 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.
老师：骚气小狂魔 @xkm88881 评分：10.0分 评价：【艺名】：#骚气小狂魔 【价格】：800 【位置】：静安区 【联系方式】 @xkm88881 【身材样貌】： 真心想约老师的，结果一步到位，一看老师频道露全脸的，绝对是良心老师，因为95%的老师不是AI照片就是美颜的，骚老师人照合一，增加体验感，所见即所得，今天老师非常满意，享受的服务都是专属服务，一定要认准露全脸的良心老师 【服务过程】：进门骚老师就热情迎面过来，yyy和ab面，全部服务一遍，然后是女上，后入视角很炸裂，最后后入交货，还有事后萧，真心推荐ly们出击，良心老师，下次还会cj 反馈人：AdrianeRan 魔都探花男群：https://t.me/+mhw016G0xDo0ZWI1
老师：七七 @qiqi_541 评分：8.5分 评价：有段时间没cj了，等到台风天一过，就决定试试小车。老师刚好换了教室，感觉闲杂人稍多，需要注意下。进门后确实是非常小巧一个妹子，但是一眼就能看到胸前的曲线。脱了衣服先去洗澡，洗浴间有点小，里间基本只能站下我一个，这点希望后续可以改进。但老师态度很好，还是认真帮我清洗和擦干。然后转战床上，吹箫环节她含得比较深，嘴巴湿热，舌头灵活，吸吮有节奏，从蛋蛋到顶端不停打转，中间会抬头看我一眼，确认我的反应。时间撑得住，直到我喊停才停下戴套。接着开始正戏，老师女上起手，小穴够紧，插入过程顺滑，包裹感明显。胸偏硬，但是捏起来手感也不算太坏。边做老师边眼神迷离的望着我，可惜实在是一段时间没做过，抽插不久后就败下阵来，顺利发射。该说不说时间太短确实让人意犹未尽，期待下次调整状态二战。不过老师表示理解，事后依旧态度温和动作轻柔，不催不赶。整个过程服务完整，态度端正，没有敷衍感。 整体而言小穴紧，口活…
老师：泡泡 @chuanghuan0618 评分：9.0分 评价：出于情怀去cj了用了琉璃醉账号的妹子，就叫她新琉璃吧。客观评价新琉璃ls的硬件与服务在这个价位段非常能打：皮肤巨滑手感巨好，奶子不到C但非常挺拔圆润，大腿光滑紧致，小穴无阴唇无异味非常好舔，服务方面有陪浴、szx、大蟒蛇以及ab面调情服务，女上也很给力，正反骑马都会。资料也没什么水份，基本就是本人真照，bio里那段学生装挨操的视频也是本人，我在第二p的时候还非常恶趣味地让她穿上那身学生装服务，视觉享受也非常刺激了，是绝对值得二刷、三刷的存在。 不过如果一定要鸡蛋里挑骨头，说些缺点的话，那就是服务过程本身偏流程化，叫床稍显刻意，少了一丝情绪价值。 之所以聊起这个也是因为刚进门的时候，新琉璃ls就在问我琉璃醉ls是怎么服务的，为什么大家对她念念不忘。我当时没有想好，现在总结一下，老琉璃最大的特点就是一切都不流程化：从浴室的拥吻到卧室的服务再到非常的自然叫床反馈，一切都…
老师：七月 @syi006 评分：9.0分 评价：出差回来想要摸个鱼按摩，看到群里有心ls，果断联系出击，教室是在一个极大的小区里，停车位有点难找，但是楼栋一眼就能找到，到了教室看到ls人小小一只，戴着眼镜，车头灯也很亮，直接长在了我心巴上。因为刚出差回来有点累选择了95套餐，付了水费就去洗澡了，回到房间ls已经换好衣服了，值得一提的是给我擦身的时候还给我体验了一把跪式服务，这点比较意外，擦干了就躺床上开始服务，服务很完美时间也很足，事后还有事后萧，算是惊喜满满。有机会值得二刷 反馈人：Kevin_chen 魔都探花男群：https://t.me/+mhw016G0xDo0ZWI1
老师：安琪 @SHaiqism 评分：10.0分 评价：昨晚结束的时候整个人还处在余韵里，脑子里一直转着她的样子，睡前都还在回味。今天忍不住直接又约了一次加课，安琪秒回，语气还是一样软软的，完全没有不耐烦。 第二次见面气氛明显更放松。安琪问我想怎么玩，自己先把衣服一件件脱掉，动作不急不慢，带着点试探又很自然。过程中安琪会时不时贴过来说话，声音轻轻的，偶尔还会笑一下，那种亲近感比昨晚更明显。 加课的部分她接受得很快，全程没有推托，节奏由我掌控，安琪只负责配合和回应。结束后安琪还靠在旁边歇了一会儿，问我这次有没有比昨晚更舒服。 两天连续约，体验是连贯的，越往后越放得开。这种感觉挺难得，已经在考虑第三次了。 反馈人：上帝之手 魔都探花男群：https://t.me/+mhw016G0xDo0ZWI1
老师：知夏 @zhixiabb1 评分：9.0分 评价：这次约知夏是下午场，人到得挺准时。 进门后气氛比较快进入状态。她先帮我宽衣，动作不算扭捏。前戏从接吻开始，吻得比较认真，舌头有回应。接着胸推，软肉夹着上下动，力度适中，摩擦感清楚。吹箫环节她含得比较深，嘴巴湿热，舌头绕着顶端打转，吸吮有节奏，中间会抬头看我一眼，确认我的反应。时间撑得住，没有草草结束。 正戏进入的时候，小穴紧，水已经出来了，插入过程顺滑，包裹感明显。抽插几下后水声就起来了，润滑够用。她一开始偏被动，后来会跟着节奏轻轻抬腰，腿也主动缠上来一点。换了侧入和后入，她都配合，没有抗拒。干到后面她里面开始有规律地收缩，喘息也重了，高潮时夹得比较紧，身体有明显的绷紧和放松。 中间休息的时候她没有马上躲到一边，而是靠着我，简单聊了两句。第二次做的时候她明显更放开一点，主动扭了几下腰，水也更多。 事后清理她比较自觉，直接用嘴把残留处理干净，动作轻，不催不赶。整个过程服务完整…
老师：安琪 @SHaiqism 评分：9.0分 评价：位置近地铁口好找，课室环境是温馨的风格，一进门寒暄几句，感觉老师亲和力很强，浴罢开始服务，老师开始展示她的口技，多次深喉，时间够长，要不是耐力还行真要交代在老师的口技之下，顶住了口活的刺激接下来就是69，下面很干净（恶趣味上来戳了几下老师的菊花，老师说可以插菊花喔，课费加2)。69过后戴上雨伞开始让老师女上开桩（这是一个错误的决定😭），老师边摇边用小嘴吮吸我的舌头，老师上下齐发力，结果没顶住，被秒了😞。平时也算这正常水平，今天是真遇到对手了，为了发泄不甘，狠狠拍了两下老师的肥臀。战斗结束后，在沙发上陪老师温存许久，比起口活和女上功力，老师情绪价值也是强项。总之这个价位绝对是天花板之一 反馈人：匿名 魔都探花男群：https://t.me/+mhw016G0xDo0ZWI1
老师：云栖 @yunxi64 评分：10.0分 评价：@yunxi64 第一次选在台风天出击，风大雨大，小区老小区，方便停车，到楼下 老师已经在楼下迎接了，这个还让我比较意外，老师穿着jk 配合一脸童颜，学生气息铺面而来，一看看中跟着老师上门， 老师客厅的大沙发又大又舒软，房间很亮，环境独居室，环境比较好，比较干净，坐着闲聊了一会 ，轻轻的握着老师的手莹白如玉，柔若无骨。摸着舒服极了，她缓缓向我靠拢我突然翻身压着他， 大蟒蛇暴力亲吻上去，老师动情的回复，舌头柔软灵动，异常甘甜，二弟立马一柱擎天，交了水费脱衣一早，没要陪浴，迅速洗完，老师也再脱衣去洗，看到老师把jk 脱掉才发现，以为是A 的熊，居然有C+ 身材也不是主干类型的， 有点肉，屁股也很大，真人不露相啊，更是异常满意，双双洗完之后上床，老师换了一身黑丝内衣加丝袜，然后妹子先来一个大蟒蛇，然后三点口，老师侧身扭头一边看着我一边深喉，口技一绝，包裹干很强，很少遇到这种不抽烟 …
老师：知夏 @zhixiabb1 评分：10.0分 评价：进门看见老师穿着白色情趣内衣和裙子，年轻漂亮，老师笑容很迷人。人照相符，感觉真人比照片更好看，真人更灵动。跟老师聊天得知老师不抽烟，在我这里大加分。常规交费之后，老师陪洗帮洗，我要求老师给我水中萧，她同意了，真好真舒服。接着去床上，老师皮肤白嫩光滑，摸起来很舒服，有舌吻，我给老师舔逼逼一会儿，一股热流流淌出来，才反应过来是老师高潮了，给哥们整兴奋了，以前在黄片里面看过的画面，黄片照见现实，哈哈哈。第一次爱爱的时候又喷了一次，屌感也非常好。老师叫床呻吟声音自然好听，让人性欲很燃，性爱加速器。第二次爱爱又高潮了两次，身体一颤一颤的，老师水特别多。不虚此行，非常愉快开心的一个下午，让人心情舒适，必返。 反馈人：为何期待 魔都探花男群：https://t.me/+mhw016G0xDo0ZWI1
老师：网红花店老板娘 @plploe 评分：9.0分 评价：#报告模版 请附上聊天记录及付款记录 【验证留名】 爱漂的大🐔 【验证时间】：7.22 【修车水费】：包夜 【服务内容】：表上都有 【凶器罩杯】：胸很大，奶头很粉 【体验细节】：早就想约老板娘了，奈何自己钱包没多少钱，所以一直在筹钱，怎么样也要吃顿好的。交了2000定金约了一个包夜。想体验MV情节。 想拍视频，他家有一个支架放在后面全程跟拍。 想要肛塞屁股，她都给我安排起来了。夜深人静的时候我们在他家的楼道玩了小遛狗。 双马尾好可爱呀。把她的头按在我的胯下。抓住。把我的大肉棒塞到她的樱桃小嘴里面。 两个手按住她的头。小嘴巴一前一后的顶着我的大鸡巴。真骚。全上海就她胆子最大了吧。晚上你叫她裸奔都可以。她的脸不化妆也好好看。特别是眼角下面的美人痣很有诱惑力，声音很嗲，很嗲。一说话就想让你操她。像我这种平常不爱说话的男人真喜欢这种主动的又可爱的小乖狗。搞了几次累了…
老师：徐小雨 @xuxiaoyu520 评分：9.0分 评价：第一次听到小雨给我发语音我是有点意外的，有一点萌，又有一点乖。当天我正冲浪，和海水搏斗一天被打的浑身酸痛，深刻领会人类的渺小和海洋的可怕之后带着疲惫的身躯回到酒店，床上听到小雨的的声音，酥麻，适度的抚慰。我也给她发了语音，还给她发了我身材照，聊骚了几个来回，毕竟，没有一点铺垫的纯CJ对我来说毫无意义。对地方口音不是很了解，大致猜想小雨是个南方姑娘。本来我是找机会去深圳的，后来在频道里看到她来了上海。那可太好了，我从海岛回到上海的第二天就约上了她。 那天异常的炎热，进到门内的一瞬间凉快下来，小雨躲在门后叫了一声男神，我一把抱住她，开始舌吻。舌吻和轻吻她的乳房有五分钟，我甚至没有拿下我的背包。然后在沙发上拥吻。洗澡，小雨把我洗的干干净净，抚摸我的胸腹，感慨我有结实肌肉，我真的信了。回到床上是快乐的时光，我问小雨妹妹是什么颜色，她说蝴蝶外黑内粉，我说那就是Black Pin…
❤1
老师：小玫瑰 @meigui0619 评分：10.0分 评价：人照基本一致，颜值8分，身材9分，偏瘦娇小，比较戳我xp。 🌹服务属于天花板级别，不论是进门的问候🐍，还是助浴👄，随后床上AB+毒龙，一般人估计直接交代了。 历经千难万险坚持到正戏，女上🌹直接化身打桩机，本想多整些动作，但顶到头的感觉着实顶不住，交代了。但🌹并没有放过我，依然强行让我坚持了几分钟，有种被qj的感觉。 结束后也不急不催，助浴+水果+小礼物轮番上阵，女友感爆棚。 🌹最后询问有没有不足的地方，看来她是真的想经营好，硬是要说不足，有两点： 1.着实坚持不了多久（其他老师那边都能坚持很久） 2.结合其他反馈来看，🌹的服务基本不会见人下菜，我更想享受专属服务😉 当然两个不足点纯属扯淡，冲就完了。 反馈人：匿名 魔都探花男群：https://t.me/+mhw016G0xDo0ZWI1
Showing the 12 most recent of 68 posts we hold for @maodutanhua. 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 — 22,391 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 2 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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“魔都探花报告赏析” (@maodutanhua), 6,172 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/maodutanhua.
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.