Channel
@zhaonanmo
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
11,257subscribers
-2,611 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003707648115 |
|---|---|
| Type | Channel |
| Username | @zhaonanmo |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/zhaonanmo |
Adult — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 15:38 | 11,257 | -497 |
| 15 Sept 2026, 12:40 | 11,754 | -2,161 |
| 13 Sept 2026, 23:37 | 13,915 | -1 |
| 12 Sept 2026, 09:18 | 13,916 | +2 |
| 10 Sept 2026, 07:57 | 13,914 | +4 |
| 6 Sept 2026, 23:40 | 13,910 | +9 |
| 4 Sept 2026, 10:19 | 13,901 | +3 |
| 2 Sept 2026, 21:19 | 13,898 | +1 |
| 1 Sept 2026, 17:58 | 13,897 | +5 |
| 31 Aug 2026, 21:28 | 13,892 | +3 |
| 30 Aug 2026, 22:46 | 13,889 | +4 |
| 29 Aug 2026, 20:27 | 13,885 | +3 |
| 28 Aug 2026, 18:27 | 13,882 | +9 |
| 27 Aug 2026, 17:35 | 13,873 | +5 |
| 26 Aug 2026, 20:00 | 13,868 | no change |
| 26 Aug 2026, 19:45 | 13,868 | first reading |
4 posts held, back to 26 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 14 pages 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.
| Window | Rolling 30 days · latest post in window 1 September 2026 |
|---|---|
| Posts held | 4 (26 August 2026 – 1 September 2026) |
| Views total | 622 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 19:30 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.
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.
糖心集团反差少妇专区 交易流程：1：发送个人资料给客服匹配少妇，2：确定少妇后付款500元-2000元门槛，给你少妇联系方式对接，确定见面时间和地点，见面满意则服务开始，不满意30分钟内及时提出反馈，可全额退款。3：如果是因客户的问题，失约则不退还门槛费 糖心集团与富婆商定给您的服务费是单次服务6000元(2-4小时)，处男：12000服务质量越高服务费就越高（当场支付给您）,您是否能接受？ 1. 单次服务：陪洗澡 性服务 服务时间： 2-4小时薪水：5000元 2. 包夜服务项目；聊天，吃饭，洗澡，性服务 服务时间:白天 7-8小时 薪水：10000元 3. 服务之前必须支付预约金500元 确定您本人不会违约才可以为您预约服务 您服务完之后平台收取百分之二十 反差少妇每月必须支付男生5W元起的生活费，以及包含男生的所有食宿开销。 认准糖心集团号码 +88801475952 一键收藏糖心集团 https://t.me…
留学回国少妇29 找身材好活好的 168/55 每月出资5W起 咨询下单联系 月儿 @bydb_01 咨询下单联系 V姐 @bydb_02 咨询下单联系 菜菜 @bydb_03 咨询下单联系 杰哥 @bydb_07 咨询下单联系 小梦 @bydb_08 咨询下单联系 婷婷 @bydb_09 糖心集团机器人： @bydbVIP_bot
昆明26 找身材好活好的单男 160/50 每月出资5W起 咨询下单联系 月儿 @bydb_01 咨询下单联系 V姐 @bydb_02 咨询下单联系 菜菜 @bydb_03 咨询下单联系 杰哥 @bydb_07 咨询下单联系 小梦 @bydb_08 咨询下单联系 婷婷 @bydb_09 糖心集团机器人： @bydbVIP_bot
杭州G奶 养活好器大弟弟 165/60 每月出资5W起 咨询下单联系 月儿 @bydb_01 咨询下单联系 V姐 @bydb_02 咨询下单联系 菜菜 @bydb_03 咨询下单联系 杰哥 @bydb_07 咨询下单联系 小梦 @bydb_08 咨询下单联系 婷婷 @bydb_09 糖心集团机器人： @bydbVIP_bot
Showing the 4 most recent of 4 posts we hold for @zhaonanmo. 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.
Named by 6 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“糖心集团反差少妇专区” (@zhaonanmo), 11,257 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/zhaonanmo.
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.